Sunday, April 13, 2014

How to change password in Oracle Transportation Management(OTM)

How to change password in Oracle Transportation Management(OTM)

If you want to change other usernames/passwords, then the list expands beyond that. I believe the the following is a complete list of OTM DB users:
glogowner
glogdba
glogdev
glogload
archive
build
reportowner


Step 1: Shutdown OTM application services.

a) Stop the Web Server



b) Stop the Application Server



Step 2: Change the database passwords.
Use alter command to change the passwords

Step 3: Encode the password for GLOG.
i) Run the below command to encode the password
java glog.util.appclass.Base64Encoding


java glog.util.appclass.Base64Encoding

ii)
Backup for glog.properties.

iii)
Update glog.properties


glog.crypto.password.mode=Encrypt

For glogdba password update following property



glog.database.password=



For glogload password update following property



glog.database.load.password=

Step 4: Start application services for OTM.

How to control Oracle Management Agent .... Part 3(How to troubleshoot Errors related to startup of Management Agent)

How to troubleshoot Errors related to startup of Management Agent:
If the EM agent is not starting we have to check the emctl.log file and the also $AGENT_INSTANCE_HOME/sysman/logs directory for more logs.
Below are some common issues and hint to troubleshoot them,

1 Management Agent starts up but is not ready
The Management Agent goes through the following process when it starts up:

a.Starting up (the Management Agent has just received the request to start up and is going to start the initialization sequence)

b.Initializing (the Management Agent is iterating over each of its components and is initializing them)

c.Ready (All components have been initialized and the Management Agent is ready to accept requests)

The command to start the Management Agent (emctl start agent) has a default timeout of 120 seconds. At the end of that timeout, it will return control to the caller and will indicate what the last state of the Management Agent was when it returns control. Depending on the number of targets being monitored by the Management Agent, step 2 listed above could take a long time and it is possible that when the command exits, the state of the agent is "Initializing" and the command reports that the "agent is running but is not ready".

You can increase the timeout by setting an environment variable "EMAGENT_TIME_FOR_START_STOP". The value should indicate the number of seconds to wait before returning control to the caller.

2 Management Agent fails to start because of time zone mismatch between agent and OMS
The Management Agent uses the time zone set in emd.properties file. During the install process of the Management Agent, the agent and the host target are registered with the OMS along with the time zone. If the Management Agent's time zone is modified at any point after the installation, the OMS will signal the Management Agent to shut down as soon as it detects this mismatch.

To reset the Management Agent's time zone, run the following command:

emctl resettz agent

3 Agent fails to start due to possible port conflict
If the Management Agent cannot start and emctl reports that there is a possible port conflict, check the Management Agent's port (based on emd.properties:EMD_URL) and see if there is another application, such as another agent, running on the machine that is already bound to the port.

To resolve this issue, stop the application currently bound to the Management Agent's port.

4 Agent secure/unsecure fails
Securing or unsecuring of the Management Agent can fail if the password to secure the agent against the OMS is incorrect or if the OMS is locked or down. You can find the reason for the failure in the /sysman/log/secure.log file.

How to control Oracle Management Agent .... Part 2 (How to control Oracle Management Agent in Windows)

How to stop, start Management Agent on Windows

Installation of Oracle Management Agent on a Windows system, creates one new service in the Services control panel.
From that control pannel you can start and stop the services

Component Service Name Format Description
Oracle Management Agent
  OracleAgent
For example:

OracleOraHome1Agent
 Use this to start and stop the Management Agent.


If you have problem in stoping in Windows NT platform (not to other Windows platforms, such as Windows 2000 or Windows XP systems) You can also use the below command to stop agent.

$PROMPT> \bin\emctl istop agent
After stopping the Management Agent using the emctl istop agent command, start the Management Agent using the Services control panel.


How to check the Status of the Management Agent on Windows:

To check the status of the Management Agent on Windows systems:

1.Change directory to the following location in the AGENT_INSTANCE_HOME directory:

AGENT_INSTANCE_HOME\bin
2.Enter the following emctl command to check status of the Management Agent:

$PROMPT> emctl status agent

How to control Oracle Management Agent ....Part 1

How to control Oracle Management Agent

Below are the activities mainly requeired for working with OEM Agent. We need the emctl utility to control this.


  1. How to stop, start, and check status of Management Agent on UNIX
  2. How to stop, start Management Agent on Windows
  3. How to check the Status of the Management Agent on Windows
  4. How to troubleshoot Errors related to startup of Management Agent 


How to stop, start, and check status of Management Agent on UNIX:

When you start the agent on UNIX systems, it starts the parent watchdog process and the child Java process for the agent. The watchdog monitors the agent Java process and attempts to start it if it fails abnormally.

To start, stop, or check the status of the Management Agent on UNIX systems:

1.You have to go to the AGENT_INSTANCE_HOME/bin directory.

2.Need to run the emctl command with appropriate parameter

Below is an example to stop an agent

$PROMPT> cd AGENT_INSTANCE_HOME/bin
$PROMPT> emctl stop agent

Command:
emctl start agent
 Starts the Management Agent

emctl stop agent
 Stops the Management Agent

emctl status agent
 it shows the status

$ ./emctl status agent
Oracle Enterprise Manager 12c Release 3 Cloud Control 12.1.0.3.0
Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.
---------------------------------------------------------------
Agent Version     : 12.1.0.2.0
OMS Version       : 12.1.0.2.0
Protocol Version  : 12.1.0.1.0
Agent Home        : /scratch/aime/work/agtbase7453/agent_inst
Agent Binaries    : /scratch/aime/work/agtbase7453/core/12.1.0.3.0
Agent Process ID  : 7834
Parent Process ID : 7781
Agent URL         : https://slc01lwi.us.oracle.com:3872/emd/main/
Repository URL    : https://slc01lwi.us.oracle.com:4900/empbs/upload
Started at        : 2013-06-05 01:33:33
Started by user   : aime
LLast Reload       : (none)
Last successful upload                       : 2013-06-20 22:17:50
Last attempted upload                        : 2013-06-20 22:17:50
Total Megabytes of XML files uploaded so far : 20.08
Number of XML files pending upload           : 0
Size of XML files pending upload(MB)         : 0
Available disk space on upload filesystem    : 62.89%
Collection Status                            : Collections enabled
Heartbeat Status                             : Ok
Last attempted heartbeat to OMS              : 2013-06-20 22:17:49
Last successful heartbeat to OMS             : 2013-06-20 22:17:49
Next scheduled heartbeat to OMS              : 2013-06-20 22:18:49
---------------------------------------------------------------

Important OS command related to printer

Please go thoroughly with the below commands in OS uses.

  1. lpadmin
  2. lpstat
  3. lpoptions 

lpadmin -p -E -v 'socket://:9100' -m -D 'Description' -L 'Lebel'
lpstat -a
lpoptions -d printer_name

Command to do active duplicate for Oracle Database

1. First login to target server 2. Validate tns connectivity between Source DB and Target DB 3. Prepare and validate space availability 4. S...