Tuesday, July 29, 2008

Installing new NLS...

I was asked to install an new NLS language on our excisting EBS environment. I had never done this before, usally the NLS is installed during a fresh install of EBS. This time I had to install the German language next to our US end NL languages.

Installing a new language is one thing, I downloaded the German langugae cd from e-delivery. This is a patch that can be installed, so no problem so far. I also downloaded the online help patch from Metalink and started patching.

But how to get the new language one the same pacthlevel as our other languages ? Should you look into every patch ever applied ?? I searched Metalink for a answer and found the following note 252422.1. According to this note Oracle provides you a synchronization patch for your NLS languages. All you have to do is run a perl script $AD_TOP/bin/adgennls.pl
This script genrates an manifest $APPL_TOP/admin/$TWO_TASK/out/adgennls.txt you should upload to Oracle (see the note for prereqs etc..)
I created the manifest for our test enviroment and it looks like this :

# Release: 11i# Active languages: D, NL, US# Manifest generated by adgennls.pl 115.7
abm admin/import/US abmactwk.dis 115.1 D:115.1:0 NL:115.1:0

abm admin/import/US abmcowk.dis 115.1 D:115.1:0 NL:115.1:0
abm admin/import/US abmdepwk.dis 115.1 D:115.1:0 NL:115.1:0
abm admin/import/US abmexpwk.dis 115.1 D:115.1:0 NL:115.1:0
abm admin/import/US abmmatwk.dis 115.1 D:115.1:0 NL:115.1:0
abm patch/115/discover/US abmactaccdaseflo.eex 115.7 D:115.7:0 NL:115.7:0
abm patch/115/discover/US abmactaccdavaflo.eex 115.6 D:115.6:0 NL:115.6:0
abm patch/115/discover/US abmactaccflo.eex 115.5 D:115.5:0 NL:115.5:0
abm patch/115/discover/US abmactbao.eex 115.5 D:115.5:0 NL:115.5:0
abm patch/115/discover/US abmactdrvflo.eex 115.5 D:115.5:0 NL:115.5:0
abm patch/115/discover/US abmactdrvsrcflo.eex 115.5 D:115.5:0 NL:115.5:0

The NL and D files are compared to the US files. If different your NLS is patched by the patch deliverd by Oracle.
So far, I have recieved a Dutch synchronization patch.

Wednesday, July 23, 2008

Agent upload fails...ret = -2

For some time now, I had some trouble with a database instance in OEM. The agent refused to upload his data to the OMS, giving me the Failed to upload file Bxxxxxx.xml, ret = -2 error.
In the log file, the following error occurs :

Thread-4595721 ERROR upload: Failed to upload file B0012907.xml, ret = -22008-07-23
Thread-4595721 WARN upload: FxferSend: received http error in header from repository: http://oemrepository/em/upload/

I bounced the agent, the OMS...even patched the OMS, but nothing solved this problem. Until I noticed the same problem in a forum. I tried the following on the target machine..

oemagent@oebs04:(state)> rm *
oemagent@oebs04:(collection)> rm *
oemagent@oebs04:(upload)> rm *
oemagent@oebs04:(emd)> rm lastupld.xml
oemagent@oebs04:(emd)> rm agntstmp.txt
oemagent@oebs04:(emd)> rm blackouts.xml
oemagent@oebs04:(emd)> cd ..
oemagent@oebs04:(sysman)> cd ../bin
oemagent@oebs04:(bin)> ./emctl clearstate agent
Oracle Enterprise Manager 10g Release
Copyright (c) 1996, 2006 Oracle Corporation. All rights reserved.
EMD clearstate completed successfully
oemagent@oebs04:(bin)> ./emctl start agent
Oracle Enterprise Manager 10g Release
Copyright (c) 1996, 2006 Oracle Corporation. All rights reserved.
Starting agent ........ started.
oemagent@oebs04:(bin)> ./emctl reload agent
Oracle Enterprise Manager 10g Release
Copyright (c) 1996, 2006 Oracle Corporation. All rights reserved.
EMD reload completed successfully
oemagent@oebs04:(bin)> ./emctl upload agent
Oracle Enterprise Manager 10g Release
Copyright (c) 1996, 2006 Oracle Corporation. All rights reserved.
EMD upload completed successfully
oemagent@oebs04:(bin)> ./emctl status agent
Oracle Enterprise Manager 10g Release
Copyright (c) 1996, 2006 Oracle Corporation. All rights reserved.
Agent Version :
OMS Version :
Protocol Version :
Agent Home : /oebs/oemagent/10.1.0
Agent binaries : /oebs/oemagent/10.1.0
Agent Process ID : 14591
Parent Process ID : 14588
Agent URL : http://oebs04.control.publicsoft.nl:1831/emd/main/
Started at : 2008-07-23 08:52:23
Started by user : oemagent
Last Reload : 2008-07-23 08:52:38
Last successful upload : 2008-07-23 08:52:52
Total Megabytes of XML files uploaded so far : 2.75
Number of XML files pending upload : 1
Size of XML files pending upload(MB) : 0.02
Available disk space on upload filesystem : 47.02%
Agent is Running and Ready

And this solved the problem !

Tuesday, July 22, 2008

OEM problem solved...

The problem mentioned before has been solved. Like most of us suspected, there was a synonym missing.

2 from all_synonyms
3 where synonym_name like 'MGMT_VIEW_UTIL';

no rows selected

SQL> create public synonym MGMT_VIEW_UTIL FOR MGMT_VIEW_UTIL;

Synonym created.

After creating the synonym, the reports look fine. I believe this porblem was caused by the export/import from the sysman schema.

Friday, July 18, 2008

Timezone in OEM ?

I am facing a strange problem. Three days ago I tried to run a report in OEM, a database Availability History report. I have to run this report every month for a customer, but this time the output showed an error !

The report showed 'Error rendering element. Exception: ORA-00904: "MGMT_VIEW_UTIL"."ADJUST_TZ": invalid identifier'

Checking Metalink didn't help me, it seems the error has something to do with a timezone ? It's true that the OSM and the target agent have different timezones, both Europe but different counties. But this has always been the case, so why suddenly an error ?? Could it have something to so with the recent export/import of the sysman schema ?

I tried to change the timezone of the target agent by adjusting the emd.properties in the $AGENT_HOME. That did not solve the problem, even worse...the agent did not want to start anymore. I canhed the parameter back to the old timezone, hoping this would solve the problem. Reloaded the agent, bounced the oms and database. This time the agent started, but after a few seconds, when trying to upload data, the agent was killed.
Checking the emagent.trc file for errors showed me the following :

2008-07-15 16:59:48 Thread-2824600480
WARN upload: FxferSend: received fatal error in header from repository: http://amssys07.controllan.nl:4889/em/upload/FATAL_ERROR::500ORA-20603: Updating timezone region of a target is not supported. Use mgmt_target.set_agent_tzrgn() API to modify the timezone region.(target name = oebs20.control.publicsoft.nl:1830)(target type = oracle_emd)(new tzrgn = Europe/Amsterdam)(old tzrgn = Europe/Warsaw)ORA-06512: at "SYSMAN.CHECK_DUPLICATE_TARGETS", line 92ORA-04088: error during execution of trigger 'SYSMAN.CHECK_DUPLICATE_TARGETS'

It seems the timezone change was still in proces, even after changing the emd.properties again.
The following steps solved the agent problem...

oemagent@oebs20:(bin)> ./emctl resetTZ agentOracle Enterprise Manager 10g Release (c) 1996, 2006 Oracle Corporation. All rights reserved.Updating /oebs/oemagent/10.1.0/sysman/config/emd.properties...Time zone set to Europe/Warsaw.
To complete this process, you must connect to the Grid Control repository as user sysman, and execute: SQL>exec mgmt_target.set_agent_tzrgn('oebs20.control.publicsoft.nl:1830','Europe/Warsaw')

The agent did start after this, but the report still showed the same error !!!

Wednesday, July 16, 2008

CPU July 2008...

This morning I received an email from Oracle......The CPU july 2008 was released yesterday.

Tuesday, July 15, 2008


After being gone for two weeks on a holiday in Spain, I was glad to find out I was able to continu the CPU April 2008 patches (first the ATG RUP5 patches had to be applied). So, right now I am patching different UAT environments. I also checked if the CPU 072008 was already announced so I could add the july pacthes, but I did not see any announcement on Metalink. Maybe at the time I am patching the production environments...