DOYENSYS Knowledge Portal

We Welcome you to visit our DOYENSYS KNOWLEDGE PORTAL : Doyensys Knowledge Portal

Tuesday, December 27, 2016

     OID EMCTL Agent not starting due to Daylight Savings Timezone Issue

The issue was actually because of incorrect timezone daylight savings updates in the installed JDK and JRE

Simply update the timezone in your installed JDK and JRE. On the safe side I had updated the timezone for ALL the installed JDK and JRE in my entire Fusion Middleware stack.

Step 1. Rerun the reset timezone command, which will now complete successfully.

$ export TZ=Pacific/Newyork

$ ./emctl resetTZ agent

Oracle Enterprise Manager 10g Release 5 Grid Control

Copyright (c) 1996, 2009 Oracle Corporation.  All rights reserved.

Updating /app/oracle/config/instances/oid1/EMAGENT/EMAGENT/sysman/config/

Successfully updated /app/oracle/config/instances/oid1/EMAGENT/EMAGENT/sysman/config/

Login as the em repository user and run the  script:

exec mgmt_target.set_agent_tzrgn('','Pacific/Newyork')

and commit the changes

This can be done for example by logging into sqlplus and doing

SQL> exec mgmt_target.set_agent_tzrgn('','Pacific/Newyork')

SQL> commit

Step 2. As a part of the above reset command, it will ask you to run a script at the SQL prompt. But when you run that scipt, you will receive the following error:

SQL> exec mgmt_target.set_agent_tzrgn('','Pacific/Newyork');

BEGIN mgmt_target.set_agent_tzrgn('','Pacific/Newyork'); END;


ERROR at line 1:

ORA-20233: Invalid agent name

ORA-06512: at "SYSMAN.MGMT_TARGET", line 3811

ORA-06512: at line 1

Step 3. According to MOS DOC ID 388280.1, the error: ORA-20233: Invalid agent name agentmachine.domain:3872 will occur if the Agent has not successfully started even once and communicated its details to the OMS. You can confirm this by querying the MGMT_TARGETS table in the sysman schema:

SQL> select target_name, target_type from mgmt_targets where target_name like '%agentmachine.domain%';

To execute the mgmt_target.set_agent_tzrgn procedure, there should be a target of type 'oracle_emd' in this table.

And in our case we could never be able to start OID EMCTL agent before, so we followed Oracle solution for this issue. The solution was to simply ignore the error and start the emctl agent (that is "Skip the steps suggested by the mgmt_target.set_agent_tzrgn routine. These are needed only if the Agent was already communicating with the OMS and its TZ has changed.").

Step 4. Now simply start the OID emctl agent with the below command and we could start it successfully.

$ ./emctl start agent

Oracle Enterprise Manager 10g Release 5 Grid Control

Copyright (c) 1996, 2009 Oracle Corporation.  All rights reserved.

Starting agent ............................. started.
Adop is not to able to detect any valid application tier nodes
Adop is not to able to detect any valid application tier nodes

Running ADOP on 12.2 is failing at initial Validation with error “adop is not able to detect any valid application tier nodes”
Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:

Validating credentials...

Run Edition context : /u01/oracle/VIS/fs1/inst/apps/VIS_ora01/appl/admin/VIS_ora01.xml
Patch edition context: / u01/oracle/VIS/fs2/inst/apps/VIS_ora01/appl/admin/VIS_ora01.xml
*******FATAL ERROR*******
PROGRAM : (/u01/oracle/VIS /fs1/EBSapps/appl/ad/12.0.0/bin/
TIME : Wed Apr 22 04:40:38 2015
FUNCTION: ADOP::GlobalVars::_GetMandatoryArgs [ Level 1 ]
ERRORMSG: adop is not able to detect any valid application tier nodes in
ADOP_VALID_NODES table. Ensure autoconfig is run on all nodes.

[STATEMENT] Please run adopscanlog utility, using the command

"adopscanlog -latest=yes"

to get the list of the log files along with snippet of the error message corresponding to each log file.

adop exiting with status = 255 (Fail)

Upon investigation we found that Database listener is not listening ebs_patch service which is mandatory for 12.2 to work on any adop activities.
[oracle@ora01 ~]$ lsnrctl status $ORACLE_SID
LSNRCTL for Linux: Version - Production on 23-APR-2015 12:20:02
Copyright (c) 1991, 2013, Oracle.  All rights reserved.
Alias                     VIS
Listening Endpoints Summary...
Services Summary...
Service "VIS" has 2 instance(s).
  Instance "VIS", status UNKNOWN, has 1 handler(s) for this service...
  Instance "VIS", status READY, has 1 handler(s) for this service...
The command completed successfully
1)     Make sure that Database init parameter has service name ebs_patch defined
2)     Connect to Database as sysdba
sqlplus / as sysdba
SQL> show parameter service_name

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
service_names                        string      VIS, ebs_patch
                If this is there, set the parameter as below
                SQL> alter system set service_names=’ebs_patch’,’VIS’ scope=spfile;

3)     Verify init parameter LOCAL_LISTENER and  set it to <DB_NAME>_LOCAL
                                 SQL> alter system set local_listener=’VIS_LOCAL’ scope=spfile;

4)     Bounce the application & database services

No comments: