Could not start OAS node manager

i am getting this message while trying to start up the node manager (owsctl start -nodemgr)
OWS-08802: Oracle Web Listener 'node' does
not exist.
other services started okey. any idea ?

I am getting the sam message too please help
i am getting this message while trying to start up the node manager (owsctl start -nodemgr)
OWS-08802: Oracle Web Listener 'node' does
not exist.
other services started okey. any idea ?

Similar Messages

Oracle APP'S Installations Context Value Management Could not started

oracle APP'S Installations Context Value Management Could not started
how it is started

Fadi, Context Value Management runs during Rapid Install or AutoConfig to make sure the context file is in good order. If it fails at the time of the installation, then most probably you have missing components at the OS level.

Could not start NetSupport Manager Client For MacOS X because the lice

Could not start NetSupport Manager Client For MacOS X because the licence expired
"Could not start NetSupport Manager Client For MacOS X because the license file has expired."
I have a suspicion the above is a result of an old version of a program from a previous version of MACOS having been migrated, even from a PPC machine (PB17 to be exact).
My issue is how to fix it. What is the exact programme in error? What do i delete?
I have even upgraded to Leopard and the problem migrates to that(!) So clearly I have to manually sort this out. But how?
Many thanks
Anthony
reposted original 19/nov/2007 unanswered

NetSupport Manager's web site would appear to be here (found via a quick web search):
http://www.netsupportmanager.com/
They should be able to tell you how to install their product, if the download doesn't contain an uninstaller (I'm not going to register with them just to find out).
Regards

Could not start NetSupport Manager Client For MacOS X because the license e

"Could not start NetSupport Manager Client For MacOS X because the license file has expired."
I have a suspicion the above is a result of an old version of a program from a previous version of MACOS having been migrated, even from a PPC machine (PB17 to be exact).
My issue is how to fix it. What is the exact programme in error? What do i delete?
I have even upgraded to Leopard and the problem migrates to that(!) So clearly I have to manually sort this out. But how?
Many thanks
Anthony

NetSupport Manager's web site would appear to be here (found via a quick web search):
http://www.netsupportmanager.com/
They should be able to tell you how to install their product, if the download doesn't contain an uninstaller (I'm not going to register with them just to find out).
Regards

Could Not start Enterprise Management Server Service

Hi,
I have installed Oracle 8i Personal Edition 8.1.6.00 on a Win2000
machine at home.
I can connect to the database that i have created (oracleDB)
When i try and run Enterprise Manager and connect to the
database, i get
the error
"ORA- 12541: TNS: no listener"
Im guessing this is because i do not have the
'OracleOraHome81ManagementServer' service running (???)
When i try and start it from the Services MMC, i recieve the
error
"Could not start the OracleOraHome81ManagementServer servic on
Local
Computer
Error 997: Overlapped I/O operation in progress"
Can anyone help me out with this?
All other Oracle related services run fine.
I have admin privelages for the PC.
Have PATH for oracle set up correctly i think.
Any help would be much appreciated
Thanks
Martin

Try creating a repository via the Configuration Assistant first
Martin, and then start the OMS service. It worked for me.

Windows Could not start remote access auto connection manager

windows Could not start remote access auto connection manager

Hi,
It would be better to provide an ScreenShot for your problem.
Roger Lu
TechNet Community Support

Error: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]

I'm using Oracle Linux 6u6. While I'm installing openstack ( 2 node set up) using packstack, I'm getting this error:
Applying 10.245.33.37_cinder.pp
10.245.33.37_keystone.pp:                         [ ERROR ]
Applying Puppet manifests                         [ ERROR ]
ERROR : Error appeared during Puppet run: 10.245.33.37_keystone.pp
Error: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
You will find full trace in log /var/tmp/packstack/20150327-100335-ltC8Ic/manifests/10.245.33.37_keystone.pp.log
Please check log file /var/tmp/packstack/20150327-100335-ltC8Ic/openstack-setup.log for more information
Additional information:
* A new answerfile was created in: /root/packstack-answers-20150327-100336.txt
* Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components.
* Did not create a cinder volume group, one already existed
* File /root/keystonerc_admin has been created on OpenStack client host 10.245.33.37. To use the command line tools you need to source the file.
* To access the OpenStack Dashboard browse to http://10.245.33.37/dashboard .
Please, find your login credentials stored in the keystonerc_admin in your home directory.
Packages:
[root@slcai461 ~]# rpm -qa|grep keystone
python-keystoneclient-0.9.0-5.el6.noarch
python-keystone-2014.1.3-2.el6.noarch
openstack-keystone-2014.1.3-2.el6.noarch
[root@slcai461 ~]# rpm -qa|grep packstack
openstack-packstack-puppet-2014.1.1-0.12.dev1068.0.4.el6.noarch
openstack-packstack-2014.1.1-0.12.dev1068.0.4.el6.noarch
Log :
[root@slcai461 ~]# cat /var/tmp/packstack/20150327-100335-ltC8Ic/manifests/10.245.33.37_keystone.pp.log
Warning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaults
Warning: Scope(Class[Keystone]): The sql_connection parameter is deprecated, use database_connection instead.
Warning: Scope(Class[Keystone]): token_format parameter is deprecated. Use token_provider instead.
Warning: Scope(Class[Keystone::Endpoint]): The public_address parameter is deprecated, use public_url instead.
Warning: Scope(Class[Keystone::Endpoint]): The internal_address parameter is deprecated, use internal_url instead.
Warning: Scope(Class[Keystone::Endpoint]): The admin_address parameter is deprecated, use admin_url instead.
Warning: Scope(Class[Nova::Keystone::Auth]): The cinder parameter is deprecated and has no effect.
Notice: Compiled catalog for slcai461.us.oracle.com in environment production in 1.60 seconds
Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false.
   (at /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:816:in `set_default')
Notice: /Stage[main]/Keystone/Keystone_config[DEFAULT/admin_token]/value: value changed '[old secret redacted]' to '[new secret redacted]'
Notice: /Stage[main]/Keystone/Keystone_config[database/connection]/value: value changed '[old secret redacted]' to '[new secret redacted]'
Notice: /Stage[main]/Keystone::Db::Sync/Exec[keystone-manage db_sync]: Triggered 'refresh' from 3 events
Notice: /Stage[main]/Keystone/Exec[keystone-manage pki_setup]: Triggered 'refresh' from 2 events
Error: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
Wrapped exception:
Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
Error: /Stage[main]/Keystone::Service/Service[keystone]/ensure: change from stopped to running failed: Could not start Service[keystone]: Execution of '/sbin/service openstack-keystone start' returned 1: Starting keystone: [FAILED]
Notice: /Stage[main]/Keystone::Service/Service[keystone]: Triggered 'refresh' from 5 events
Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_service[neutron]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_service[neutron]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[admin]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[admin]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova_ec2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova_ec2]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinderv2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinderv2]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_service[novav3]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_service[novav3]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_tenant[services]: Skipping because of failed dependencies
Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_user[neutron]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_user[neutron]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_user[nova]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_user[nova]: Skipping because of failed dependencies
Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_user[glance]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_user[glance]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_role[admin]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_role[admin]: Skipping because of failed dependencies
Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_user_role[glance@services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_user_role[glance@services]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Endpoint/Keystone_service[keystone]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Endpoint/Keystone_service[keystone]: Skipping because of failed dependencies
Error: Could not prefetch keystone_endpoint provider 'keystone': Execution of '/usr/bin/keystone --os-endpoint http://127.0.0.1:35357/v2.0/ endpoint-list' returned 1: An unexpected error prevented the server from fulfilling your request. (HTTP 500)
Notice: /Stage[main]/Keystone::Endpoint/Keystone_endpoint[RegionOne/keystone]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Endpoint/Keystone_endpoint[RegionOne/keystone]: Skipping because of failed dependencies
Notice: /Stage[main]/Main/Keystone_service[cinder_v2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Main/Keystone_service[cinder_v2]: Skipping because of failed dependencies
Notice: /Stage[main]/Main/Keystone_endpoint[RegionOne/cinder_v2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Main/Keystone_endpoint[RegionOne/cinder_v2]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/novav3]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/novav3]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinder]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_service[cinder]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinder]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinder]: Skipping because of failed dependencies
Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_service[glance]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_service[glance]: Skipping because of failed dependencies
Notice: /Stage[main]/Glance::Keystone::Auth/Keystone_endpoint[RegionOne/glance]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Glance::Keystone::Auth/Keystone_endpoint[RegionOne/glance]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_user_role[nova@services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_user_role[nova@services]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_user[admin]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_user[admin]: Skipping because of failed dependencies
Notice: /Stage[main]/Keystone::Roles::Admin/Keystone_user_role[admin@admin]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Keystone::Roles::Admin/Keystone_user_role[admin@admin]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_user[cinder]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_user[cinder]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova_ec2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova_ec2]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinderv2]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_endpoint[RegionOne/cinderv2]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_service[nova]: Skipping because of failed dependencies
Notice: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Nova::Keystone::Auth/Keystone_endpoint[RegionOne/nova]: Skipping because of failed dependencies
Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_user_role[neutron@services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_user_role[neutron@services]: Skipping because of failed dependencies
Notice: /Stage[main]/Neutron::Keystone::Auth/Keystone_endpoint[RegionOne/neutron]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Neutron::Keystone::Auth/Keystone_endpoint[RegionOne/neutron]: Skipping because of failed dependencies
Notice: /Stage[main]/Cinder::Keystone::Auth/Keystone_user_role[cinder@services]: Dependency Service[keystone] has failures: true
Warning: /Stage[main]/Cinder::Keystone::Auth/Keystone_user_role[cinder@services]: Skipping because of failed dependencies
Notice: Finished catalog run in 3.10 seconds
Please let me know how to fix this.

This problem connected with proxy-setings.
As the first steps you should try:
       1. export system env variable:
http_proxy=http://www-proxy.ru.oracle.com:80
https_proxy=https://www-proxy.ru.oracle.com:80
no_proxy=127.0.0.1,localhost
and you can also export
    export OS_TENANT_NAME=admin
    export OS_USERNAME=admin
    export OS_PASSWORD=root
    export OS_AUTH_URL=http://<conntroller_IP>:5000/v2.0/
2. and than restart mysqld, if it is running, stop iptables and repeat installation process from beginning with the currently generated answer file
if we are exporting variable OS_PASSWORD, its value should be the same as value for CONFIG_KEYSTONE_ADMIN_PW in the currently generated answer file.
This OS_PASSWORD will be written by packstack in the /root/keystonerc_admin file and will be used as admin's password for login to Openstack dashboard.

WLS 9.2: MigrationException: Could not start JTAMT on local server

I have configured a two machine WLS 9.2 Cluster with two Managed Servers.
          When I try to start the Managed Server through the Node Manager from Admin
          Server's WLS Console, it fails with the following error (
          actually both Managed Servers fail with the same error):
          weblogic.cluster.migration.MigrationException: Could not start JTAMT on
          local server because it could not be deactivated on the current host.
          at
          weblogic.transaction.internal.TransactionRecoveryService.deployAllTransactionRecoveryServices(TransactionRecoveryService.java:400)
          at
          weblogic.transaction.internal.TransactionRecoveryService.resume(TransactionRecoveryService.java:170)
          at
          weblogic.transaction.internal.TransactionRecoveryService.start(TransactionRecoveryService.java:181)
          at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
          at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
          at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
          This message resides in file:
          bea920\weblogic92\common\nodemanager\servers\MANAGED-SERVER1\logs\MANAGED-SERVER1.log
          The WLS installation was done including the Node Manager Service.
          Is this error message familiar at all and what could be done to fix it?
          These Managed Servers run on Win2000 and Win2003 respectively. Should I do
          something to the OS (Enable XA Txs in Control Panel/MSDTC)?

Did you start AdminServer before try to start MANAGED-SERVER1?
          Did you ever migrate Transaction Recovery Service of MANAGED-SERVER1 to other servers?
          If the problem still exist, you can enable the debug option "DebugJTAMigration" and post the stack trace.

Workflow could not start in HCM process and Forms

Hi All
It would be really helpful if you can suggest possible solution regarding case management case in HCM forms and process.
I have set up a simple custom HCM process and Form regarding Infotype 2 updation. I have checked the process and form consistency and it seems fine. Now when I run the process from HRASR_DT it generates a process number but it also gives an error workflow could not start.I get following error (SWIA log - Step history)
Executing flow work item - Transaction brackets of the workflow has been damaged
Exception occurred - Error when starting work item 000000007031
PROCESS_NODE - Error when processing node '0000000014' (ParForEach index 000000)
CREATE - Error when creating a component of type 'Step'
CREATE_WIM_HANDLE - Error when creating a work item
CREATE_VIA_WFM - Exit CL_HRASR00_POBJ_WF_EXIT triggered exeception for event CREATED and (target) status
EVENT_RAISED - Error updating the process object
Executing flow work item - Exit CL_HRASR00_POBJ_WF_EXIT triggered exeception for event STATE_CHG and (target) status READY->ERROR
EVENT_RAISED - Error updating the process object
Executing flow work item - Transaction brackets of the workflow has been damaged
Executing flow work item - Work item 000000007031: Object FLOWITEM method EXECUTE cannot be executed
Executing flow work item - Error when processing node '0000000014' (ParForEach index 000000)
I have searched few SAP notes such as 1384961 which talks about same error but it is implemented in our system (EA-HR 604 , Patch 27, )
Appreciate any help.
Thanks
Umang

Hi Swati
One of the similar (not exact) issues were resolved by correcting the event linkage....please refer thread:
http://scn.sap.com/message/14848795#14848795
Not sure of the details of the the resolution, maybe Ragavendran Kanagaraj can throw more light.
Just some high level checks (if not done already):
Check event linkage errors in SWEQADM if anything is related to your WF
Check in SWEL if it's showing any more details (not sure if it will)
Any warnings in syntax check of WF template (PFTC) or WF definition (SWDD)
Any error sin binding
regards,
Modak

CRS could not start after reboot

I installed oracle 10g R2 RAC on RHEL4 U4 with 2 nodes. It runs fine on 2 nodes (without reboot after installation). But when I rebooted one node, I found that the CRS daemon could not start automatically. The boot menu show "Starting CRS" [OK]. The "init.crs start" command won't init the CRS daemon.
$ ./crs_stat
CRS-0184: Cannot communicate with the CRS daemon.
SQL> conn / as sysdba
Connected to an idle instance.
SQL> startup
ORA-01078: failure in processing system parameters
ORA-01565: error in identifying file '+DATA1/RAC/spfileRAC.ora'
ORA-17503: ksfdopn:2 Failed to open file +DATA1/RAC/spfileRAC.ora
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
$ /etc/init.d/init.crs start
Startup will be queued to init within 90 seconds.
$ cat /etc/inittab
id:5:initdefault:
# Run xdm in runlevel 5
x:5:respawn:/etc/X11/prefdm -nodaemon
h1:35:respawn:/etc/init.d/init.evmd run >/dev/null 2>&1 </dev/null
h2:35:respawn:/etc/init.d/init.cssd fatal >/dev/null 2>&1 </dev/null
h3:35:respawn:/etc/init.d/init.crsd run >/dev/null 2>&1 </dev/null
$ ls /etc/rc5.d
K01tog-pegasus K35smb K85mdmpd S05openibd S18rpcidmapd S55sshd S96readahead
K02NetworkManager K35vncserver K87auditd S06cpuspeed S19rpcgssd S56rawdevices S97messagebus
K05saslauthd K35winbind K87ipmi S08arptables_jf S19vmware-tools S56xinetd S97rhnsd
K10dc_server K40smartd K89netplugd S08iptables S25netfs S58ntpd S98cups-config-daemon
K10psacct K50ibmasm K90bluetooth S09isdn S26apmd S80sendmail S98haldaemon
K12dc_client K50netdump K94diskdump S10network S26lm_sensors S85gpm S99local
K15httpd K50snmpd K96pcmcia S12syslog S27vasd S90crond
K20nfs K50snmptrapd S00microcode_ctl S13irqbalance S28autofs S90xfs
K24irda K50tux S01sysstat S13portmap S29oracleasm S95anacron
K25squid K73ypbind S04readahead_early S14nfslock S44acpid S95atd
K30spamassassin K74nscd S05kudzu S15mdmonitor S55cups S96init.crs
Do I miss any configuration to initialize the CRSD at boot?
thanks, ezlee

did you run cluster verification utility for node connectivity?
http://docs.oracle.com/cd/E11882_01/rac.112/e16794/cvu.htm#autoId19
also check the logs ad $GRID_HOME/log/<hostname>/...
starting with alert.log, then the ones its referencing

CRS-0215: Could not start resource

Hello
This is my first time installing clusterware. However, i have not been too successful at it. This is my configuration:
Operating System: RHES 5.3
Oracle Database 11gR1
OpenFiler used to configure shared disks
After several attempts, i was able to run the root.sh script on both nodes.
Output on first node:
[root@vx0301 oracle]# /u01/app/oraInventory/orainstRoot.sh
Changing permissions of /u01/app/oraInventory to 770.
Changing groupname of /u01/app/oraInventory to oinstall.
The execution of the script is complete
[root@vx0301 oracle]# /u01/crs11g/root.sh
Checking to see if Oracle CRS stack is already configured
/etc/oracle does not exist. Creating it now.
Setting the permissions on OCR backup directory
Setting up Network socket directories
Oracle Cluster Registry configuration upgraded successfully
clscfg: EXISTING configuration version 4 detected.
clscfg: version 4 is 11 Release 1.
Successfully accumulated necessary OCR keys.
Using ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.
node <nodenumber>: <nodename> <private interconnect name> <hostname>
node 1: vx0301 vx0301-priv vx0301
node 2: vx0302 vx0302-priv vx0302
clscfg: Arguments check out successfully.
NO KEYS WERE WRITTEN. Supply -force parameter to override.
-force is destructive and will destroy any previous cluster
configuration.
Oracle Cluster Registry for cluster has already been initialized
Startup will be queued to init within 30 seconds.
Adding daemons to inittab
Expecting the CRS daemons to be up within 600 seconds.
Cluster Synchronization Services is active on these nodes.
vx0301
Cluster Synchronization Services is inactive on these nodes.
vx0302
Local node checking complete. Run root.sh on remaining nodes to start CRS daemons.
Output on second node:
[root@vx0301 oracle]# /u01/app/oraInventory/orainstRoot.sh
Changing permissions of /u01/app/oraInventory to 770.
Changing groupname of /u01/app/oraInventory to oinstall.
The execution of the script is complete
[root@vx0301 oracle]# /u01/crs11g/root.sh
Checking to see if Oracle CRS stack is already configured
/etc/oracle does not exist. Creating it now.
Setting the permissions on OCR backup directory
Setting up Network socket directories
Oracle Cluster Registry configuration upgraded successfully
clscfg: EXISTING configuration version 4 detected.
clscfg: version 4 is 11 Release 1.
Successfully accumulated necessary OCR keys.
Using ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.
node <nodenumber>: <nodename> <private interconnect name> <hostname>
node 1: vx0301 vx0301-priv vx0301
node 2: vx0302 vx0302-priv vx0302
clscfg: Arguments check out successfully.
NO KEYS WERE WRITTEN. Supply -force parameter to override.
-force is destructive and will destroy any previous cluster
configuration.
Oracle Cluster Registry for cluster has already been initialized
Startup will be queued to init within 30 seconds.
Adding daemons to inittab
Expecting the CRS daemons to be up within 600 seconds.
Cluster Synchronization Services is active on these nodes.
vx0301
vx0302
I also got the errors:
Starting GSD application resource on (2) nodes1:CRS-0215: Could not start resource 'ora.vx0301.gsd'
Starting ONS application resource on (2) nodes1:CRS-0215: Could not start resource 'ora.vx0301.ons'
There were no log files.
When i clicked ok on the execute scripts page, i got the following errors in the configuration assistants page:
Output generated from configuration assistant "Oracle Notification Server Configuration Assistant":
Command = /u01/crs11g/install/onsconfig add_config vx0301:6251 vx0302:6251
The ONS configuration failed to create
Configuration assistant "Oracle Notification Server Configuration Assistant" failed
The "/u01/crs11g/cfgtoollogs/configToolFailedCommands" script contains all commands that failed, were skipped or were cancelled. This file may be used to run these configuration assistants outside of OUI. Note that you may have to update this script with passwords (if any) before executing the same.-----------------------------------------------------------------------------Output generated from configuration assistant "Oracle Notification Server Configuration Assistant":
Command = /u01/crs11g/install/onsconfig add_config vx0301:6251 vx0302:6251
The ONS configuration failed to create
Configuration assistant "Oracle Notification Server Configuration Assistant" failed
The "/u01/crs11g/cfgtoollogs/configToolFailedCommands" script contains all commands that failed, were skipped or were cancelled. This file may be used to run these configuration assistants outside of OUI. Note that you may have to update this script with passwords (if any) before executing the same.-----------------------------------------------------------------------------Output generated from configuration assistant "Oracle Notification Server Configuration Assistant" (attempt 2):
Command = /u01/crs11g/install/onsconfig add_config vx0301:6251 vx0302:6251
The ONS configuration failed to create
Configuration assistant "Oracle Notification Server Configuration Assistant" failed
The "/u01/crs11g/cfgtoollogs/configToolFailedCommands" script contains all commands that failed, were skipped or were cancelled. This file may be used to run these configuration assistants outside of OUI. Note that you may have to update this script with passwords (if any) before executing the same.-----------------------------------------------------------------------------
Contents of the /u01/crs11g/cfgtoollogs/configToolFailedCommands script:
[oracle@vx0301 ~]$ cat /u01/crs11g/cfgtoollogs/configToolFailedCommands
# Copyright (c) 1999, 2007, Oracle. All rights reserved.
/u01/crs11g/install/onsconfig add_config vx0301:6251 vx0302:6251
/u01/crs11g/bin/oifcfg setif -global eth0/172.30.4.0:public eth1/192.168.1.0:cluster_interconnect
/u01/crs11g/bin/cluvfy stage -post crsinst -n vx0301,vx0302
I tried running /u01/crs11g/install/onsconfig add_config vx0301:6251 vx0302:6251 manually from the terminal:
[root@vx0301 oracle]# /u01/crs11g/install/onsconfig add_config vx0301:6251 vx0302:6251
The ONS configuration failed to create
Output of the ons.log file:
[root@vx0301 oracle]# cat /u01/crs11g/log/vx0301/racg/ons.log
Oracle Database 11g CRS Release 11.1.0.6.0 - Production Copyright 1996, 2007 Oracle. All rights reserved.
2010-01-25 13:59:15.786: [    RACG][3055679168] [10113][3055679168][default]: clsrons: procr_init:PROC-32: Cluster Ready Services on the local node is not running Messaging error [9] status = 32
2010-01-25 13:59:33.359: [    RACG][3055584960] [10229][3055584960][default]: clsrons: procr_init:PROC-32: Cluster Ready Services on the local node is not running Messaging error [9] status = 32
2010-01-25 14:01:00.319: [    RACG][3086849728] [10734][3086849728][default]: clsrons: procr_init:PROC-32: Cluster Ready Services on the local node is not running Messaging error [9] status = 32
2010-01-25 14:02:02.723: [    RACG][3086628544] [11105][3086628544][default]: clsrons: procr_init:PROC-32: Cluster Ready Services on the local node is not running Messaging error [9] status = 32
[root@vx0301 oracle]#
I am absoutely stumped as to what to do next. Any help is greatly appreciated.

I tried running ruclufvy.sh stage -post crsinst -n vx0301,vx0302 -verbose. Here is the output:
[oracle@vx0301 clusterware]$ ./runcluvfy.sh stage -post crsinst -n vx0301,vx0302 -verbose
Performing post-checks for cluster services setup
Checking node reachability...
Check: Node reachability from node "vx0301"
Destination Node Reachable?
vx0301 yes
vx0302 yes
Result: Node reachability check passed from node "vx0301".
Checking user equivalence...
Check: User equivalence for user "oracle"
Node Name Comment
vx0302 passed
vx0301 passed
Result: User equivalence check passed for user "oracle".
Checking Cluster manager integrity...
Checking CSS daemon...
Node Name Status
vx0302 running
vx0301 running
Result: Daemon status check passed for "CSS daemon".
Cluster manager integrity check passed.
Checking cluster integrity...
Node Name
vx0301
vx0302
Cluster integrity check passed
Checking OCR integrity...
Checking the absence of a non-clustered configuration...
All nodes free of non-clustered, local-only configurations.
Uniqueness check for OCR device passed.
Checking the version of OCR...
OCR of correct Version "2" exists.
Checking data integrity of OCR...
ERROR:
OCR integrity is invalid.
OCR integrity check failed.
Checking CRS integrity...
Checking daemon liveness...
Check: Liveness for "CRS daemon"
Node Name Running
vx0302 yes
vx0301 yes
Result: Liveness check passed for "CRS daemon".
Checking daemon liveness...
Check: Liveness for "CSS daemon"
Node Name Running
vx0302 yes
vx0301 yes
Result: Liveness check passed for "CSS daemon".
Checking daemon liveness...
Check: Liveness for "EVM daemon"
Node Name Running
vx0302 yes
vx0301 yes
Result: Liveness check passed for "EVM daemon".
Liveness of all the daemons
Node Name CRS daemon CSS daemon EVM daemon
vx0302 yes yes yes
vx0301 yes yes yes
Checking CRS health...
Check: Health of CRS
Node Name CRS OK?
vx0302 yes
vx0301 unknown
Result: CRS health check failed.
CRS integrity check failed.
Checking node application existence...
Checking existence of VIP node application
Node Name Required Status Comment
vx0302 yes exists passed
vx0301 yes exists passed
Result: Check passed.
Checking existence of ONS node application
Node Name Required Status Comment
vx0302 no exists passed
vx0301 no exists passed
Result: Check passed.
Checking existence of GSD node application
Node Name Required Status Comment
vx0302 no exists passed
vx0301 no exists passed
Result: Check passed.
Post-check for cluster services setup was unsuccessful on all the nodes.
[oracle@vx0301 clusterware]$
I also tried running ./ocrchek on both nodes. Here is the output:
[oracle@vx0301 bin]$ ./ocrcheck
Status of Oracle Cluster Registry is as follows :
Version : 2
Total space (kbytes) : 3306636
Used space (kbytes) : 2056
Available space (kbytes) : 3304580
ID : 1425438992
Device/File Name : /dev/sdb1
Device/File integrity check failed
Device/File not configured
Cluster registry integrity check failed
[oracle@vx0301 bin]$ ssh vx0302
Last login: Mon Jan 25 13:52:03 2010 from vx0301
[oracle@vx0302 ~]$ cd /u01/crs11g/bin/
[oracle@vx0302 bin]$ ./ocrcheck
Status of Oracle Cluster Registry is as follows :
Version : 2
Total space (kbytes) : 3306636
Used space (kbytes) : 2056
Available space (kbytes) : 3304580
ID : 1425438992
Device/File Name : /dev/sdb1
Device/File integrity check failed
Device/File not configured
Cluster registry integrity check failed
[oracle@vx0302 bin]$
From the results, the ids are the same, and so is the OCR disk. But the integrity check has failed. How do i interpret this output?

[wls8.1 sp.3] cannot remote start with node manager on another server

In this domain run on 2 physical servers in windows 2003. In machine that has admin server can start with node manager but another machine without admin server cannot remote start . when i remote start , the node manager has facing error messages as below:
# AT "node manager monitoring" in weblogic admin console
[[NodeManager:300033]Could not execute command ping on the node manager. Reason: weblogic.nodemanager.NodeManagerException: [CommandInvoker: Failed to send command: 'ping to server 'null' to NodeManager at host: 'xxx.xxx.xxx.24:5555' with exception Connection reset by peer.. Please ensure that the NodeManager is active on the target machine].]
# AT "nodemanger.log" has facing error messages as below:
<Aug 20, 2008 7:34:07 PM ICT> <Info> <[email protected]:5555> <NodeManage r started, log messages being written into file C:\bea\WEBLOG~1\common\NODEMA~1\ NodeManagerLogs\NodeManagerInternal\nm_server02_08_20_2008-19_34_03.log>
<Aug 20, 2008 7:59:58 PM ICT> <Warning> <Security> <BEA-090476> <Invalid/unknown SSL header was received from peer server01 - 10.208.50.23 during SSL handsha ke.> <Aug 20, 2008 8:00:11 PM ICT> <Warning> <Security> <BEA-090476> <Invalid/unknown SSL header was received from peer server01 - xxx.xxx.xxx.23 during SSL handsha key.>
I would REALLY appreciate any suggestions as to what might be the cause or what i could try.
Thanks ....

Hi,
It is up to you to decide whether you want to use nodemanager or not.
It does not make any difference if the server is started via script or nodemanager.
if i want everything (AS, MS, and NM) to come up at server boot i need to set each of them up as windows services (which is what i have at the moment) but this wont allow me to use the node manager ==> Yes this statement is correct.
You can either set AS and MS as windows service (or) AS and nodemanager as service.
Thanks,
Sharmela

SDM Deployment Failed--SDM could not start the J2EE cluster on the DB Host

HI,
I am trying to deploy ESS packges in EP through SDM.But while deploying I am getting this error in SDM at the start itself:-
Error: An error occured while starting a cluster instance.
Oct 14, 2008 5:14:41 PM Error: There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage
Please check if there is an appropriate running cluster instances
SDM could not start the J2EE cluster on the host SBPEPDB1! The online deployment is terminated.
There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage
I am pasting the full LOG File details:-
Oct 14, 2008 6:32:00 PM Info: Starting cluster instance processes.
Oct 14, 2008 6:32:00 PM Error: An error occured while starting a cluster instance.
Oct 14, 2008 6:32:00 PM Error: There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage . The instances, returned by MessageServer [MS host: SBPEPCI1; MS port: 3900], are :
Name:JM_T1223989073901_0_CPCAPP109
Host:SBPEPCI1
State:5
HostAddress:172.17.131.38
Name:JC_CPCAPP109_EPP_01
Host:CPCAPP109
State:5
HostAddress:172.17.131.31
Please check if there is an appropriate running cluster instances.
Oct 14, 2008 6:32:00 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Oct 14, 2008 6:32:00 PM Error: Aborted: development component 'pcui_gp/isr/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'2515722'/'0', grouped by software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0':
SDM could not start the J2EE cluster on the host SBPEPDB1! The online deployment is terminated.
There is no clutser control instance running on host SBPEPDB1 which is described in SecureStorage .
The instances, returned by MessageServer [MS host: SBPEPCI1; MS port: 3900], are :
Name:JM_T1223989073901_0_CPCAPP109
Host:SBPEPCI1
State:5
HostAddress:172.17.131.38
Name:JC_CPCAPP109_EPP_01
Host:CPCAPP109
State:5
HostAddress:172.17.131.31
Please check if there is an appropriate running cluster instances.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Oct 14, 2008 6:32:04 PM Info: Starting to save the repository
Oct 14, 2008 6:32:05 PM Info: Finished saving the repository
Oct 14, 2008 6:32:07 PM Info: Starting: Initial deployment: Selected software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0' will be deployed.
Oct 14, 2008 6:32:07 PM Error: Aborted: software component 'SAPPCUI_GP'/'sap.com'/'MAIN_ERP05VAL_C'/'1000.600.0.13.0.20080516101947''/'0':
Failed deployment of SDAs:
development component 'pcui_gp/isr/cfg'/'sap.com'/'MAIN_ERP05VAL_C'/'2515722'/'0' : aborted
Please, look at error logs above for more information!
I have checked the CONFIGTOOl and the properties seem to be OK.
I tried SHUTTING DOWN all APPLICATION servers & Restarting the DEPLOYMENT,but it still Failed
Pls suggest.
Regards,
Abhijeet
I

Hi George,
Thnx for your reply.
I have stopped all Application servers and kept only the CI-DB instances running.Retried deploying the ESS packages but still getting the same error.
Have checked the Visual admin,it is not in SAFE mode,it working normally.
Have alos checked the CLUSTER Manager Property Values in both Visual Admin & Config Tool,they are alright.
About the Cluster Resources,can you pls specify what exactly do you mean by "Cluster Resources are running or not".
I think if the application servers are stopped,then the Cluster resources shudnt come into play right?? Correct me if I am wrong.
Kindly suggest what other steps I shud take.
Regards,
Abhijeet

Database Studio 7.9.08.09 - Could not access to user management; Deleting old settings and reinstallation did not bring a change -- database studio deinstallation cannot be performed anymore

Hi Community,
for a few months I have been struggling with a SAP Max DB database Studio issue and finally, I had to give up the idea of being able to fix this on my own. I am desperately seeking for help and I hope that you may be able to give me a hint, advice or even a solution.
This is what happened:
I used to run Windows 7 on 32bit. I also had Database Studio installed - which was running fine then.
After a harware upgrade, I am running now Windows 7 on a 64 bit System. All my files from my local disk (C:\) have been restored and copied onto my new system.
I reinstalled Database Studio Version 7.9.08.09 onto my new System. But on the first try to start the program I received the error that said "Could not Access to user Management.See Window -> Show View-> Event Log Viewer for more Details."
However the Event Log Viewer was empty.
After searching the web for a solution, I followed the advice given in this community and deinstalled Database Studio and deleted the C.\Users\MyAccount\sdb folder manually.
I reinstalled Database Studio and started it as Administrator.
However, the error is still appearing.
And, what makes it even worse is : now I am not able to uninstall Database Studio anymore.
When I run SAP MaxDB Installation Manager and select the instance of database Studio to be uninstallled I am receiving the error:
"ERR: Unhandled Exception: Can't call method: "GenPackageList" on an undefined value at SDB/Install/Gui/Dialogs/SelectInstance.pm line 328"
Any advice is highly appreciated.
Thanks,
Agnieszka

Hello Yashwanth,
thank you for your quick Response.
Yes, I downloaded and installed the 64 bit Version of dbstudio.
I downloaded and ran the following .exe file: maxdb-studio-win-64bit-x86_64-7_9_08_09.exe
I am running the following Java-Version:
Java Plug-in 1.6.0_45
Using JRE version 1.6.0_45-b06 Java HotSpot(TM) Client VM
I myself am not a SAP customer. However, the Company I am working for is a SAP customer.
Can you explain in Detail, how to create a ticket with SAP?
Thanks,
Agnieszka

The Sun Java System Application Server could not start

Hello All,
I downloaded the Java Pet Store example from sun's website and followed the instructions for installation. After successful installation, I tried to deploy the project and gave the following error
C:\Documents and Settings\sina\My Documents\Projects\services\nbproject\build-impl.xml:194: Deployment error:
The Sun Java System Application Server could not start.
More information about the cause is in the Server log file.
Possible reasons include:
- IDE timeout: refresh the server node to see if it's running now.
- Port conflicts. (use netstat -a to detect possible port numbers already used by the operating system.)
- Incorrect server configuration (domain.xml to be corrected manually)
- Corrupted Deployed Applications preventing the server to start.(This can be seen in the server.log file. In this case, domain.xml needs to be modified).
- Invalid installation location.
See the server log for details.
BUILD FAILED (total time: 5 minutes 20 seconds)
The link above points to the following line in the build-impl.xml file
<nbdeploy debugmode="false" forceRedeploy="${forceRedeploy}" clientUrlPart="${client.urlPart}" clientModuleUri="${client.module.uri}"/>
Can any one help whats wrong.An early response will be highly appreciated.
Kind Regards.
Hasnain Javed.

Hi,
Maybe you already got this fix but here is a suggestion, a snippet from the readme index,html of the petstore download
# Start the Sun Java System Application Server and the JavaDB database. To do so, open a command prompt and change directory to <javaeesdk.home>/bin and issue the following commands:
asadmin start-database
asadmin start-domain
# Change directory to <petstore.home> and enter the following commands
ant setup
ant run
This will setup, build and deploy the petstore on the application server, and then launch the application homepage in your default browser.
The "ant setup" that you run from <petstore.home> (petstore.home is the directory where petstore is installed or where you unzipped it) will populate the database wth data and setup the proper database tables etc that are used by the application.
hth,
Sean

Could not start OAS node manager

Similar Messages

Maybe you are looking for