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
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
Using updates with joins is something that does not work the first time. I’ve been using Oracle, MSSQL and other DB’s before I became Oracle DBA and I always had to check resources to get it done. Now I add an other resource….
Yesterday I had a developer at my desk who accidentally dropped a few tables. Time for the Recycle Bin thingy!
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.