Hi Everyone,
I am happy to share with you that I have received Oracle ACE Award. I am really honored to receive this Award for my contribution towards Oracle community.
I would like to take this opportunity to thank all my family, friends, colleagues and followers for their support.
Please take a moment to look at my Oracle ACE profile – Satishbabu Gunukula
Regards,
Satishbabu Gunukula, Oracle ACE
http://www.oracleracexpert.com
Wednesday, February 22, 2012
Thursday, February 16, 2012
Could Not Get DeploymentManager When Deploying or Undploying Agile
When deploying and un-deploying Oracle Agile application, users may receive error "Could not get DeploymentManager”.
Problem: You will receive below error when Agile unable to deploy/un-deploy using admin_client.jar utility
Failed at "Could not get DeploymentManager".
This is typically the result of an invalid deployer URI format being supplied, the target server not being in a started state or incorrect authentication details being supplied.
More information is available by enabling logging -- please see the Oracle Containers for J2EE Configuration and Administration Guide for details.
Cause 1:- The deployment command uses opmn request port 6003 by default. You will receive the error If the install used different opmn port (6004)
Solution:- Replace the port from 6003 to 6004 in DeployAgilePLM.sh or UndeployAgilePLM.sh script
deployer:oc4j:[rmis]:opmn://host[:opmnPort]/[iASInstanceName] /oc4jInstanceName
Cause 2:- If the server name changed from fully qualified name to short name or vice versa then admin_client.jar utility unable to deploy and you will receive the error.
Solution:- Replace fully qualified name to short name or vice versa in DeployAgilePLM.sh or UndeployAgilePLM.sh script and run the script.
In some cases, the application may hang with following error message when deploying the Agile Application. It is due to the version mismatch or Admin Data Schema Version not present
07/12/11 06:26:30 Notification ==>Initialize link ends...
07/12/11 06:26:30 Notification ==>Initialize integration begins...
07/12/11 06:26:30 Notification ==>Initialize integration ends...
07/12/11 06:26:30 Notification ==>Initialize JavaClient begins...
07/12/11 06:26:30 Notification ==>Initialize JavaClient ends...
07/12/11 06:26:30 Notification ==>Started application : Agile
07/12/11 06:26:30 Notification ==>Binding web application(s) to site default-web-site begins...
07/12/11 06:26:30 Notification ==>Binding application web-module for application Agile to site default-web-site under context root Agile
07/12/11 06:26:31 Notification ==>Initializing Servlet: com.agile.ui.pcm.InitServlet for web application application
You will see below message in default_group_home_default_group_1.log
07/12/11 13:26:32 ++++++++++++++++++++++++++++++++++++++++++++++++
07/12/11 13:26:32 + +
07/12/11 13:26:32 + Admin Data Schema Version NOT PRESENT!!!
07/12/11 13:26:32 + Admin Server Schema Version : 9.3.185.0
07/12/11 13:26:32 + +
07/12/11 13:26:32 ++++++++++++++++++++++++++++++++++++++++++++++++
Solution: Install the correct version or enter correct database information in agile.properties files, if version mismatch. Please refer Note 569229.1 for more information.
Please refer the link How to Deploy and Un-deploy Agile application.
Regards,
Satishbabu Gunukula
http://www.oracleracexpert.com
Problem: You will receive below error when Agile unable to deploy/un-deploy using admin_client.jar utility
Failed at "Could not get DeploymentManager".
This is typically the result of an invalid deployer URI format being supplied, the target server not being in a started state or incorrect authentication details being supplied.
More information is available by enabling logging -- please see the Oracle Containers for J2EE Configuration and Administration Guide for details.
Cause 1:- The deployment command uses opmn request port 6003 by default. You will receive the error If the install used different opmn port (6004)
Solution:- Replace the port from 6003 to 6004 in DeployAgilePLM.sh or UndeployAgilePLM.sh script
deployer:oc4j:[rmis]:opmn://host[:opmnPort]/[iASInstanceName] /oc4jInstanceName
Cause 2:- If the server name changed from fully qualified name to short name or vice versa then admin_client.jar utility unable to deploy and you will receive the error.
Solution:- Replace fully qualified name to short name or vice versa in DeployAgilePLM.sh or UndeployAgilePLM.sh script and run the script.
In some cases, the application may hang with following error message when deploying the Agile Application. It is due to the version mismatch or Admin Data Schema Version not present
07/12/11 06:26:30 Notification ==>Initialize link ends...
07/12/11 06:26:30 Notification ==>Initialize integration begins...
07/12/11 06:26:30 Notification ==>Initialize integration ends...
07/12/11 06:26:30 Notification ==>Initialize JavaClient begins...
07/12/11 06:26:30 Notification ==>Initialize JavaClient ends...
07/12/11 06:26:30 Notification ==>Started application : Agile
07/12/11 06:26:30 Notification ==>Binding web application(s) to site default-web-site begins...
07/12/11 06:26:30 Notification ==>Binding application web-module for application Agile to site default-web-site under context root Agile
07/12/11 06:26:31 Notification ==>Initializing Servlet: com.agile.ui.pcm.InitServlet for web application application
You will see below message in default_group_home_default_group_1.log
07/12/11 13:26:32 ++++++++++++++++++++++++++++++++++++++++++++++++
07/12/11 13:26:32 + +
07/12/11 13:26:32 + Admin Data Schema Version NOT PRESENT!!!
07/12/11 13:26:32 + Admin Server Schema Version : 9.3.185.0
07/12/11 13:26:32 + +
07/12/11 13:26:32 ++++++++++++++++++++++++++++++++++++++++++++++++
Solution: Install the correct version or enter correct database information in agile.properties files, if version mismatch. Please refer Note 569229.1 for more information.
Please refer the link How to Deploy and Un-deploy Agile application.
Regards,
Satishbabu Gunukula
http://www.oracleracexpert.com
How to Deploy and Un-deploy Oracle Agile Application
Whenever you are applying the patches to Oracle Agile environment, you need to Un-deploy and deploy the application.
Before you apply the patch you must Un-deploy the Agile application. After successful installation of the patch you must deploy the agile application in order to take effect of the applied patch.
Un-Deploy Agile application:-Go to Agile home directory and run below command
$ cd $/agileDomain/bin
$./ UndeployAgilePLM.sh
Where password is the oc4jadmin user password
12/02/09 14:04:10 Notification ==>Application UnDeployer for Agile STARTS.
12/02/09 14:04:11 Notification ==>Removing all web binding(s) for application Agile from all web site(s)
12/02/09 14:04:19 Notification ==>Application UnDeployer for Agile COMPLETES.
Follow the steps to apply a Patch in Oracle Agile environment
1. Check PMN processes are running on the Agile Server.
2. Stop the OPMN processes
$ opmnctl stopall
3. Unzip the patch to a temporary directory
For Unix
$/tmp//Install_Patch.sh
For Windows
C:\temp\\Install_Patch.bat
You will get a message “Is the Agile Application already undeployed? (y/n) “. You must enter Y inorder to proceed further.
Ignore the message "Enter Passphrase for keystore:" and let the installation continue
When the installation is completed, the “INSTALLATION SUCCESSFUL” message will appear and press the return key to complete the installation.
4. Start OPMN processes
$ opmnctl startall
Deploy Agile application:-After successful installation of the patch deploy the Agile application
$ cd $/agileDomain/bin
$./DeployAgilePLM.sh
Where password is the oc4jadmin user password
12/02/09 14:06:50 Notification ==>Application Deployer for Agile STARTS.
………………………
……………………….
12/02/09 14:07:35 Notification ==>Binding web application(s) to site default-web-site ends...
12/02/09 14:07:35 Notification ==>Application Deployer for Agile COMPLETES. Operation time: 45434 msecs
Check the status of the agile application
$ opmnctl status
Make sure to check applied patch from application. If Deploy and Un-deploys fails with some reason then you will not see the applied patch in Application.
. Launch the application and login
. Click on help --> About Agile
. You should see the patch number under “updated versions”
Regards,
Satishbabu Gunukula
http://www.oracleracexpert.com
Before you apply the patch you must Un-deploy the Agile application. After successful installation of the patch you must deploy the agile application in order to take effect of the applied patch.
Un-Deploy Agile application:-Go to Agile home directory and run below command
$ cd $
$./ UndeployAgilePLM.sh
Where password is the oc4jadmin user password
12/02/09 14:04:10 Notification ==>Application UnDeployer for Agile STARTS.
12/02/09 14:04:11 Notification ==>Removing all web binding(s) for application Agile from all web site(s)
12/02/09 14:04:19 Notification ==>Application UnDeployer for Agile COMPLETES.
Follow the steps to apply a Patch in Oracle Agile environment
1. Check PMN processes are running on the Agile Server.
2. Stop the OPMN processes
$ opmnctl stopall
3. Unzip the patch to a temporary directory
For Unix
$/tmp/
For Windows
C:\temp\
You will get a message “Is the Agile Application already undeployed? (y/n) “. You must enter Y inorder to proceed further.
Ignore the message "Enter Passphrase for keystore:" and let the installation continue
When the installation is completed, the “INSTALLATION SUCCESSFUL” message will appear and press the return key to complete the installation.
4. Start OPMN processes
$ opmnctl startall
Deploy Agile application:-After successful installation of the patch deploy the Agile application
$ cd $
$./DeployAgilePLM.sh
Where password is the oc4jadmin user password
12/02/09 14:06:50 Notification ==>Application Deployer for Agile STARTS.
………………………
……………………….
12/02/09 14:07:35 Notification ==>Binding web application(s) to site default-web-site ends...
12/02/09 14:07:35 Notification ==>Application Deployer for Agile COMPLETES. Operation time: 45434 msecs
Check the status of the agile application
$ opmnctl status
Make sure to check applied patch from application. If Deploy and Un-deploys fails with some reason then you will not see the applied patch in Application.
. Launch the application and login
. Click on help --> About Agile
. You should see the patch number under “updated versions”
Regards,
Satishbabu Gunukula
http://www.oracleracexpert.com
Tuesday, January 10, 2012
You want to participate in Oracle Beta program or Exam?
Oracle Technology Beta programs available for all Oracle technology products including Oracle Database, Oracle Enterprise manager, Oracle Fusion Middleware…etc.
Please note that Beta program is highly selective and acceptance into these programs makes you part of an elite group of test sites that are carefully selected based up on technical expertise and knowledge of Oracle productions
Why should you participate?
The main benefit is gaining access to technology before your competitors and developing a close working relationship with oracle development.
If you want to participate in Oracle beta program, please register yourself using below link.
http://otnbeta.oracle.com/bpo/prospects/index.htm
You can also contact BETAPROG_US@ORACLE.COM for details
You can also participate in Oracle Certification Beta exams. These Beta exams are pre-production exams used by Oracle to evaluate new exam questions and it will go through a rigorous development and evaluation process before being released to the public.
Beta exams are offered at a deeply discounted price and exam usually takes around 3 to 3.5 hours to complete.
To learn more information about Beta Exams, please visit
http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=182
Regards,
Satishbabu Gunukula
http://www.oracleracepxert.com
Please note that Beta program is highly selective and acceptance into these programs makes you part of an elite group of test sites that are carefully selected based up on technical expertise and knowledge of Oracle productions
Why should you participate?
The main benefit is gaining access to technology before your competitors and developing a close working relationship with oracle development.
If you want to participate in Oracle beta program, please register yourself using below link.
http://otnbeta.oracle.com/bpo/prospects/index.htm
You can also contact BETAPROG_US@ORACLE.COM for details
You can also participate in Oracle Certification Beta exams. These Beta exams are pre-production exams used by Oracle to evaluate new exam questions and it will go through a rigorous development and evaluation process before being released to the public.
Beta exams are offered at a deeply discounted price and exam usually takes around 3 to 3.5 hours to complete.
To learn more information about Beta Exams, please visit
http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=182
Regards,
Satishbabu Gunukula
http://www.oracleracepxert.com
Monday, January 9, 2012
How to STOP and START processes in Oracle RAC and Log Directory Structure
You need to follow the below steps to Stop and Start processes in Oracle RAC
Shutdown RAC Database
You need to Shutdown Database instances on each node. You can either use Oracle Enterprise Manager or SVRCTL to shutdown the instances. If you are using EM Grid control then set a blackout in Grid control for processes that you intend to shutdown. So that records for these processes indicate that the shutdown was planned.
Use below command to stop Enterprise Manager/Grid Control
$ORACLE_HOME/bin/emctl stop dbconsole
Use below command to shutdown all oracle RAC instances on all nodes.
$ ORACLE_HOME/bin/srvctl stop database -d db_name
If you want to stop specific database instances use below command
$ ORACLE_HOME/bin/srvctl stop database -d db_name –i instance_name
Shutdown Oracle ASM Instance
Once the database is stopped, proceed with ASM Instance shutdown.
Use below command to shutdown ASM instances on all nodes
$ORACLE_HOME/bin/bin/srvctl stop asm -n node
Shutdown Node applications
Use below command to shutdown node apps on all RAC nodes
$ORACLE_HOME/bin/bin/srvctl stop nodeapps -n node
Shutdown Oracle Clusterware
You need to Shutdown oracle clusterware or CRS as root and run below command on each node in the cluster.
#crsctl stop crs
Please note that using above command will stop Oracle High availability services (OHAS) and Clustware stack in a single command
From 11g R2, you can do this in two stops
1. Stop Clustwerware stack on local node
#crsctl stop cluster
You can stop the clusterware stack on all nodes in the cluster
# Crsctl stop cluster –all
Where
-all Start clusterware on all nodes
-n Start clusterware on particular nodes
2. Stop Oracle High availability service demon on each node in the cluster.
# crsctl stop has
Check the Status of Cluster
Once all process stopped run the below command to check the status of CRSD,CSSD,EVMD process.
# crsctl check crs
If you see any process failed to stop then you can also use Force option to terminate the processes unconditionally.
$ crsctl stop crs –all –f
Start processes in Oracle RAC
Follow the reverse sequence to start all processes in oracle RAC
# crsctl start crs
$ORACLE_HOME/bin/bin/srvctl start nodeapps -n node
$ORACLE_HOME/bin/bin/srvctl start asm -n node
$ORACLE_HOME/bin/srvctl start database -d db_name
If you come across any issues during startup orshutdown, check the Oracle Clusterware Component Log Files.
Oracle Clusterware Log Directory Structure
CRS_HOME/log/hostname/crsd/ - The log files for the CRS daemon CRS_HOME/log/hostname/cssd/ - The log files for the CSS daemon
CRS_HOME/log/hostname/evmd/ - The log files for the EVM daemon
CRS_HOME/log/hostname/client/ - The log files for the Oracle Cluster Registry (OCR)
CRS_HOME/log/hostname/racg/ - The log files for the Oracle RAC high availability component
CRS_HOME/log/hostname/racg/ - The log files for the Oracle RAC high availability component
CRS_HOME/log/hostanme/alert.log – The alert.log for Clusterware issues.
Please note that the CRS_HOME is the directory in which the Oracle Clusterware software was installed and hostname is the name of the node
Regards,
Satishbabu Gunukula
http://www.oracleracexpert.com
Shutdown RAC Database
You need to Shutdown Database instances on each node. You can either use Oracle Enterprise Manager or SVRCTL to shutdown the instances. If you are using EM Grid control then set a blackout in Grid control for processes that you intend to shutdown. So that records for these processes indicate that the shutdown was planned.
Use below command to stop Enterprise Manager/Grid Control
$ORACLE_HOME/bin/emctl stop dbconsole
Use below command to shutdown all oracle RAC instances on all nodes.
$ ORACLE_HOME/bin/srvctl stop database -d db_name
If you want to stop specific database instances use below command
$ ORACLE_HOME/bin/srvctl stop database -d db_name –i instance_name
Shutdown Oracle ASM Instance
Once the database is stopped, proceed with ASM Instance shutdown.
Use below command to shutdown ASM instances on all nodes
$ORACLE_HOME/bin/bin/srvctl stop asm -n node
Shutdown Node applications
Use below command to shutdown node apps on all RAC nodes
$ORACLE_HOME/bin/bin/srvctl stop nodeapps -n node
Shutdown Oracle Clusterware
You need to Shutdown oracle clusterware or CRS as root and run below command on each node in the cluster.
#crsctl stop crs
Please note that using above command will stop Oracle High availability services (OHAS) and Clustware stack in a single command
From 11g R2, you can do this in two stops
1. Stop Clustwerware stack on local node
#crsctl stop cluster
You can stop the clusterware stack on all nodes in the cluster
# Crsctl stop cluster –all
Where
-all Start clusterware on all nodes
-n Start clusterware on particular nodes
2. Stop Oracle High availability service demon on each node in the cluster.
# crsctl stop has
Check the Status of Cluster
Once all process stopped run the below command to check the status of CRSD,CSSD,EVMD process.
# crsctl check crs
If you see any process failed to stop then you can also use Force option to terminate the processes unconditionally.
$ crsctl stop crs –all –f
Start processes in Oracle RAC
Follow the reverse sequence to start all processes in oracle RAC
# crsctl start crs
$ORACLE_HOME/bin/bin/srvctl start nodeapps -n node
$ORACLE_HOME/bin/bin/srvctl start asm -n node
$ORACLE_HOME/bin/srvctl start database -d db_name
If you come across any issues during startup orshutdown, check the Oracle Clusterware Component Log Files.
Oracle Clusterware Log Directory Structure
CRS_HOME/log/hostname/crsd/ - The log files for the CRS daemon CRS_HOME/log/hostname/cssd/ - The log files for the CSS daemon
CRS_HOME/log/hostname/evmd/ - The log files for the EVM daemon
CRS_HOME/log/hostname/client/ - The log files for the Oracle Cluster Registry (OCR)
CRS_HOME/log/hostname/racg/ - The log files for the Oracle RAC high availability component
CRS_HOME/log/hostname/racg/ - The log files for the Oracle RAC high availability component
CRS_HOME/log/hostanme/alert.log – The alert.log for Clusterware issues.
Please note that the CRS_HOME is the directory in which the Oracle Clusterware software was installed and hostname is the name of the node
Regards,
Satishbabu Gunukula
http://www.oracleracexpert.com
Subscribe to:
Posts (Atom)
