Oracle Database

did you get a solution for this ??? i am getting the same error ???

looking at the logs, i have the below message

log4j:WARN No appenders could be found for logger (oracle.sysman.emSDK.svlt.EMServletUtil).
log4j:WARN Please initialize the log4j system properly.
ConnectionService.init: Get repos properties from credential store.
Repos details fetched from credstore
Fetched repository credentials from Credential Store
OMS version 11.1.0.1.0 is not compatible with repository version 10.2.0.4.0 Repository needs to be upgraded.

However, i know that our DB is 11.1.0.7.0 , so not sure why OMS thinks the version is old? any pointers?

You could have changed the port during the install gui or via the staticports.ini file if using a silent install.

As we all know, in OEM grid 11gR1 instalation, OEM has assigned it self a default port 7799 ( https://localhost.com:7799/em/console/logon/logon).

How can we change this port and which service we need to restart.

Thanks for this informative post. It help me a lot. And it gave mo ideas on how to make more money in marketing business. I hope lots of people visit this site so they can easily learn this informative post.
curt

Hi,

Enjoyed reading your article on exporting and importing database stats.

Could you give me some help, or maybe write a new page, on how to do individual tables and schemas too.

Thanks.

I second this: genius !

This just solved an hour's head scratching here in the office.

Many thanks :-)

Yes you can. Here is the syntax

ALTER TABLE <table name> RENAME CONSTRAINT <constraint name> TO <new constraint name>

Mike

can you rename constraints
thanks

yes i was doing this

thank you

Given you have posted this in the Enterprise Manager section, are you sure you are not getting confused between Grid Control and Grid Infrastructure?

Grid Control
Oracle Enterprise Manager. Used to monitor, manage and tune databases, servers, listeners and other targets.

Grid Infrastructure
A new product "grouping" introduced with Oracle 11g. Currently, it contains ASM, HAS and Clusterware.

Grid Infrastructure is need for ASM as this is how you install the ASM binaries.

Grid Control is not needed for ASM to install ASM.

Hope this helps.

Mike,

I don't know how you came across this answer, but it's genius! I was just about raise an SR with Oracle for this one having wasted the last couple of hours googling and re-installing things all to no avail when someone told me they'd seen this entry on the forum.

Thanks again!

Hi Mike,
Do you get a yellow triangle in the bottom left-hand corner of IE when the page loads? If so, you may want to check out the Known Issues section of the Grid Install guide. I updated it recently with an IE bug I came across.

Regards

oracle manual says i need grid to install asm why is this.

For some reason I cannot log onto Grid 11 using IE. Other browsers work fine (FF) but IE does not. When I click on the login button nothing happens. Has anyone come across this issue?

Thanks

Yes, see this link DB Console Install

I have seen similar behaviour on Veritas filesystems that have significant IO, but did not used ODM/Quick IO. In fact, on one system I saw drops of empty tables take 30 minutes plus. Ultimately the problem was down to how Veritas filesystems handle locking on datafiles/fielsystems. Under heavy IO the FS lock became a bottle neck and showed up as IO waits. And even though the table was empty, Oracle needs to touch the datafile and as such got stuck behind all the other activity on the FS. We encountered similar issues with truncate table too.

In the end we implemented ODM/quick IO as this significantly improves throughput on Veritas filesystems. Alternatively, if possible try an alternative filesystem. UFS instead of VxFS. Be aware, that quick IO was a cost option.

Try this link. It has some regression steps.

http://abcdba.com/abcdbarachowtoinstallrac10gonsolaris1of4

I suspect you are trying to delete archivelogs still needed for recovery and which have not been backed up. To quote the manual

RMAN-08138: WARNING: archived log not deleted - must create more backups Cause: An archived log that 
should have been deleted was not as it it did not meet the user specified archive log deletion policy of 
number of backups required before deleting the logs.

Hi - Dropping and truncating tables is taking forever on my system. I can run a create table as select * from duel and then immediatly drop it and it can take upto 15 minutes. This is an oracle 9 environment running on solaris with 1000's of updates. I have checked the waits in the database and all seems to be okay, but i am getting io waits on the veritas filesystems. How can this be on an empty table?