JInitiator: “Unable to verify the certificate – code will be treated as unsigned.”

When getting the following message using JInitiator: “Unable to verify the certificate – code will be treated as unsigned.”, please check “Control Panel > JInitiator > Cache”, to which location Java will store the ‘Oracle Jar Cache’ and JInitiator settings (like the ‘Grant Always’ setting and ‘Oracle Jar Cache’ directory) in <USERHOME>\.jinit\properties<jinit version> and jpicerts<jinit version>.

Java will get the USERHOME path from the Windows registry [HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders\Desktop] when looking for the Desktop path setting and truncates the ‘Desktop’ part. Most of the time this will result in the correct USERHOME directory, but when this setting is changed to a network path where users are not granted write access, Java is not able to store the Cache and JInitiator settings.

Ofcourse, this can be one of a few problems, but if you suspect a case like this, there might be a solution… Continue reading

Experiences with Oracle DUL

Yesterday I had my first experience with Oracle DUL.

A customer had major disk damages on his RAID 5 system, but the backups he made daily were (sadly) never tested (lesson!). Recovery gave lots off errors on UNDO segments in the system table space. Only a 10 months old export was available.

Together with a consultant from Oracle we tried to get data from two damaged databases. For one DB, DUL could read the dictionary from the system data file, but could not read all the data from the user data files. The other DB also had a corrupt system data file, which meant that DUL was unable to read the dictionary and was unable to locate data from user data files. Continue reading

Agent Configuration Assistant does not add targets

Today the Agent Configuration Assistant (Agent on 64bit Windows Server 2003, Grid Control on 32bit Windows XP) failed in running the last optional step. It hang for a long time, too long (a hour or so). After canceling this last step, checking the [configToolFailedCommands] showed the [oracle.sysman.emcp.agent.AgentPlugIn] was messing up the set-up.

Continue reading

DB instances does not wait for ASM to be finished

Yesterday, I came across a small problem with an Oracle RAC installation using ASM. After a restart of one of the three (Windows Server 2003) nodes, three of the five database instances did not start automatically…

Running ‘crs_stat’ showed status OFFLINE and target ONLINE for these instances, but strangely there was no entry in the alert log telling these instances did not start because of ’something’ was wrong. It even looked like that they did not got any signal to start at all! OK, so I checked the CRS log for any strange behavior and it showed ASM finishing after the database instances gave up starting.

A quick search on the ‘new and improved’ My Oracle Support (old Metalink), resulted in running ‘crs_stat -p’ and check for [REQUIRED_RESOURCES=] for each instance. It showed that for the particular node, ASM was not required for these three database instances. Modifying this with ’srvctl modify instance -d db1 -i node1 -s +ASM1′ (for example), did the trick.

I found this solution on Metalink: Doc ID: NOTE:276208.1 “CRS is not starting first the ASM instance”, although I can not imagine hitting this bug on 10.2.0.4.

Happy consulting!