Oracle resource manager10.2.0.4/11.2.0.2

Hello Folks,
Does Resource manager sends error back to the application or to the alert_log, does it writes any alerts to any of the trace files,
we want to get and alert in our Task Manager when ORM kicks in..!!
Thanks,
Gutha.

Hi Stefan and thanks for your suggestion.
I had a look at my glogin.sql but i had no custom entries.
I also find this metalink which more or less explains my issue in detail:
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=PROBLEM&id=311127.1
However, the directory and file that is suggested to be removed does not exist in my 102 or 112 environment.
I don't have a DBMA directory, but only a DBCA and DBMA and in those directories I do not find any *.tx files to remove.
So unfortunately I still have the issue with my hanging popup during "Getting database information..."

Similar Messages

Error while provisioning user into Oracle resource

I wrote a custom oracle resource adapter and an trying to create a new user and assign this user to the resource. I get the following error when I save the user account. "com.waveset.util.WavesetException: An error occurred connecting to resource "
I can however successfully test connection to this resource from the resources tab. Please help me figure what the issue can be.
Thanks,
Prithi Narasimhan.

Hi Prithi
Can you please send me your code so that I can test it and give you the exact reason for your failure.
But I feel if your test connection is successful I dont think you should have any problem try with different userid , password and Database. Hope it works.
Regards
Gajendra Nagapurkar

Oracle Resource Adaptor for Geronimo

For Apache Geronimo 1.1.1, an Oracle Resource Adapter was not available, so we had to write a ʻproxyʼ between the JMS queue and the Oracle Advanced queue. Is there an Oracle Resource Adapter available for Geronimo 2.1.3?
I actually want a JMS interface to Oracle's Advanced Queue product.
Regards.

i'm writin a program to extract info from SAP but i can't find where download the JCO.jar , in SAP site you need a user and password but i don't have it, dou you have already de jar file? could you send me tha jar? or may be i have to purchase that product? pleas help me!!!!
my addres is [email protected]

Oracle Profile Vs Oracle Resource Manager in Oracle 11g

Hi Friends,
Whats is the Avantages / Dis advantages of using Oracle Profile and Oracle Resource Manager to limit the oracle resources to oracle users in Oracle 11.2.0.1
Regards,
DB

If you have a single database servicing multiple Services / Applications / Schemas (e.g. a typical database consolidation), you could use Profiles and Resource Manager to place limits on resource usage by Service / Application / Schema. That way, for example, a 32 CPU database server running a single database can still limit the number of cores for each Service / Application / Schema using the Resource Manager.
Hemant K Chitale

How manuplate data on multiple tables in the oracle resource adapter

Hi all,
I have a requirement to write an resource adapter for oracle. But the key point is that, the user creation has to add entries in several tables and same goes with updation and getting the results.
Please help me with the code snippet, if any one has gone through this one already.
Can stored procedure can be executed in the normal oracle resource adapter , so that it does all the required work ? while the adapter is in quick need, friends please help me out.
Thanks,
idm developer

google 'Instead-Of Trigger', it's pretty handy

Mutliple Oracle Resource Groups Port Question

Hello,
In a 2 node cluster, (3.2, Sol10, ZFS), I have a oracle resource group running on each node with the ability to failover to the other. As each resource group has it's own listener, do the port numbers for the listeners need to be different so there is no conflict if both resource groups run on the same node?
Thx for any assistance.

That shouldn't be problem if you are having a LH as part of the oracle rg and the listener is binding to the LH.
Best Regards,
Madhan Kumar

Oracle Resource Manager

hi,
In the GROUP section of the ubb file I have defined a Oracle Resource Manager.
GRP1
LMID = SITE1 GRPNO =1
TMSNAME = TMS_ORA TMSCOUNT = 2
OPENINFO = "Oracle_XA:Oracle_XA+Acc=P/usr1/usr1+SesTm=0+LogDir=/tmp/xa_logs+Objects=T+Loose_Coupling=false+SesWt=60"
when i boot the application, the TMS_ORA gets booted.
Now if I change just the login information to another valid user (say usr2/usr2)of
the database in the OPENINFO parameter and try to boot the TMS_ORA fails.
Can you please let me know as to what can be the possible reason behind this.
Thanks

Hi,
If you are using ORACLE Version 7.X,
You should grant the SELECT privilege of v$xatrans$ to usr2.
The checking is like the following.
1. sqlplus usr2/usr2
2. desc v$xatrans$
Here, If the desc command's result gets a error, then the privilege is
not granted to usr2.
info) v$xatrans$ view table owner is sys, therefore you should login sys
using sqlplus
and then "grant select on v$xatrans$ to usr2" statement is
executed in sqlplus prompt.
3. reboot TMS.
If you are using ORACLE Version 8.X,
Maybe, You should grant the SELECT privilege of DBA_PENDING_TRANSACTIONS
view table to usr2.
The checking is like the following.
1. sqlplus usr2/usr2
2. desc dba_pending_transactions
Here, If the desc command's result gets a error, then the privilege is
not granted to usr2.
info) DBA_PENDING_TRANSACTIONS view table owner is sys, therefore you
should login sys using sqlplus
and then "grant select on dba_pending_transactions to usr2"
statement is executed in sqlplus prompt.
3. reboot TMS.
This hopes help.
Thanks.
"vipul" <[email protected]> wrote in message
news:[email protected]..
>
hi,
In the GROUP section of the ubb file I have defined a Oracle ResourceManager.
>
GRP1
LMID = SITE1 GRPNO =1
TMSNAME = TMS_ORA TMSCOUNT = 2
OPENINFO ="Oracle_XA:Oracle_XA+Acc=P/usr1/usr1+SesTm=0+LogDir=/tmp/xa_logs+Objects=T+L
oose_Coupling=false+SesWt=60"
>
>
when i boot the application, the TMS_ORA gets booted.
Now if I change just the login information to another valid user (sayusr2/usr2)of
the database in the OPENINFO parameter and try to boot the TMS_ORA fails.
Can you please let me know as to what can be the possible reason behindthis.
>
Thanks

Oracle Resource Adapter in Waveset Lighthouse

We are running Waveset 4.1 (20040620 SP2). We want to use the Oracle Resource Adapter to facilitate automatic de-provisioning within Waveset upon employee termination in Oracle HR (8i DB). The Lighthouse technical reference only provides scant details on how to set up the resource in Waveset which we have done. Where do we go from here? With the acquisition of Waveset by Sun, documentation seems to be hard to come by. If someone could point me in the right direction, I would appreciate it.
Andy

When your activeSync process runs against OracleHR, a form that is designated in the Resource Configuration is processed. This is where you map all of the Oracle attributes to Lighthouse (IDM) attributes.
In this form, you can control the actions taken based upon the feedOp variable.
Check out the /samples/forms directory for example activeSync forms.
Mat

Oracle resource group

Hi,
I need some help, I'm going to setup oracle HA under sun cluster 3.1. We will put 1 oracle instance but will be having several database instances running. My question is do I need to create a seperate resource group for each database instance?
Any help/advise is greatly appreciated.
Thanks.

If serveral oracle server instances depends on a disk storage resource in a resource group, can these oracle resources be seperated into different groups? In other words, is cross-group resource dependency allowed in Solaris?
One more question on oracle resource. Supposing there are a few oracle server resources and one disk storage resource in a resource group and the oracle resources depends on storage resource. if anyone of the oracle resources failover, wil it cause the whole resource group to failover? How about if the storage resource fails?

Oracle resource restart

Could someone clarify my confusion with restarting resources.
I have a 2 node SC 3.2 with a single oracle database.
The customers requirement is that if there is a failure of oracle database or listener then the cluster tries to restated the resource, but doesnt initiate a failover.
The Failover mode for the Oracle server and oracle listener resources are set to RESTART_ONLY.
The Oracle server resource has a retry count= 1 and a retry interval = 300
the listener resource retry count= 3 and a retry interval = 300
What I have found during testing of the listener resource is that it works, as I expect, if I kill the listener process 3 times within 5 minutes then the cluster restarts the service. If I kill it once more the cluster then reports that it has exceeded retry count and doesnt initiate a failover ... All good.
However, at what appears to be 5 minutes after the first restart, with no administrator intervention, the cluster restarts the resource. What is controlling this restart and how can I turn it off ?
Thanks

Hi Tim
I have the same problem for both listener and oracle resources, ie if I repeatedly kill the process the cluster restarts the resource upto the retry count, which is as designed, but then at 5 minutes after first restart the resource is restarted.
Following is the listener log and the listener resource configuration.
I'll work on getting the messages file and setting debugging. Thanks
cat /var/opt/SUNWscor/oracle_listener/message_log.omadb-listener
Feb 27 12:30:59 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: Attempting to restart listener LISTENER_OmaT.
Feb 27 12:31:00 SC[SUNWscor.oracle_listener.monitor_stop]:omadb-rg:omadb-listener: Stopping fault monitor using pmfadm tag ORALSNR_MON_omadb-listener
Feb 27 12:31:01 SC[SUNWscor.oracle_listener.stop]:omadb-rg:omadb-listener: listener LISTENER_OmaT is not running.
Feb 27 12:31:02 SC[SUNWscor.oracle_listener.start]:omadb-rg:omadb-listener: Starting listener LISTENER_OmaT.
Feb 27 12:31:02 SC[SUNWscor.oracle_listener.start]:omadb-rg:omadb-listener: Using method 'run_setuid_prog' to execute start commands
LSNRCTL for Solaris: Version 10.2.0.3.0 - Production on 27-FEB-2008 12:31:02
Copyright (c) 1991, 2006, Oracle. All rights reserved.
Starting /appl/oma-dm/oracle/product/10.2.0.3.64/bin/tnslsnr: please wait...
TNSLSNR for Solaris: Version 10.2.0.3.0 - Production
System parameter file is /var/opt/oracle/listener.ora
Log messages written to /appl/oma-dm/oracle/product/10.2.0.3.64/network/log/listener_omat.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=172.23.118.52)(PORT=1521)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=172.23.193.21)(PORT=1521)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=omaT)(PORT=1521)))
STATUS of the LISTENER
Alias LISTENER_OmaT
Version TNSLSNR for Solaris: Version 10.2.0.3.0 - Production
Start Date 27-FEB-2008 12:31:03
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /var/opt/oracle/listener.ora
Listener Log File /appl/oma-dm/oracle/product/10.2.0.3.64/network/log/listener_omat.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=172.23.118.52)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=172.23.193.21)(PORT=1521)))
Services Summary...
Service "OmaT" has 1 instance(s).
Instance "OmaT", status UNKNOWN, has 1 handler(s) for this service...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
Executing command: /opt/SUNWscor/oracle_listener/bin/oracle_listener_manage start
Feb 27 12:31:06 SC[SUNWscor.oracle_listener.start]:omadb-rg:omadb-listener: Listener LISTENER_OmaT started.
Feb 27 12:31:07 SC[SUNWscor.oracle_listener.monitor_start]:omadb-rg:omadb-listener: Starting monitor
Feb 27 12:31:39 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: listener LISTENER_OmaT probe successful.
Feb 27 12:32:09 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: Attempting to restart listener LISTENER_OmaT.
Feb 27 12:32:10 SC[SUNWscor.oracle_listener.monitor_stop]:omadb-rg:omadb-listener: Stopping fault monitor using pmfadm tag ORALSNR_MON_omadb-listener
Feb 27 12:32:11 SC[SUNWscor.oracle_listener.stop]:omadb-rg:omadb-listener: listener LISTENER_OmaT is not running.
Feb 27 12:32:12 SC[SUNWscor.oracle_listener.start]:omadb-rg:omadb-listener: Starting listener LISTENER_OmaT.
Feb 27 12:32:12 SC[SUNWscor.oracle_listener.start]:omadb-rg:omadb-listener: Using method 'run_setuid_prog' to execute start commands
LSNRCTL for Solaris: Version 10.2.0.3.0 - Production on 27-FEB-2008 12:32:12
Copyright (c) 1991, 2006, Oracle. All rights reserved.
Starting /appl/oma-dm/oracle/product/10.2.0.3.64/bin/tnslsnr: please wait...
TNSLSNR for Solaris: Version 10.2.0.3.0 - Production
System parameter file is /var/opt/oracle/listener.ora
Log messages written to /appl/oma-dm/oracle/product/10.2.0.3.64/network/log/listener_omat.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=172.23.118.52)(PORT=1521)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=172.23.193.21)(PORT=1521)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=omaT)(PORT=1521)))
STATUS of the LISTENER
Alias LISTENER_OmaT
Version TNSLSNR for Solaris: Version 10.2.0.3.0 - Production
Start Date 27-FEB-2008 12:32:13
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /var/opt/oracle/listener.ora
Listener Log File /appl/oma-dm/oracle/product/10.2.0.3.64/network/log/listener_omat.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=172.23.118.52)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=172.23.193.21)(PORT=1521)))
Services Summary...
Service "OmaT" has 1 instance(s).
Instance "OmaT", status UNKNOWN, has 1 handler(s) for this service...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
Executing command: /opt/SUNWscor/oracle_listener/bin/oracle_listener_manage start
Feb 27 12:32:16 SC[SUNWscor.oracle_listener.start]:omadb-rg:omadb-listener: Listener LISTENER_OmaT started.
Feb 27 12:32:17 SC[SUNWscor.oracle_listener.monitor_start]:omadb-rg:omadb-listener: Starting monitor
Feb 27 12:32:49 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: Attempting to restart listener LISTENER_OmaT.
Feb 27 12:32:49 SC[SUNWscor.oracle_listener.monitor_stop]:omadb-rg:omadb-listener: Stopping fault monitor using pmfadm tag ORALSNR_MON_omadb-listener
Feb 27 12:32:50 SC[SUNWscor.oracle_listener.stop]:omadb-rg:omadb-listener: listener LISTENER_OmaT is not running.
Feb 27 12:32:51 SC[SUNWscor.oracle_listener.start]:omadb-rg:omadb-listener: Starting listener LISTENER_OmaT.
Feb 27 12:32:51 SC[SUNWscor.oracle_listener.start]:omadb-rg:omadb-listener: Using method 'run_setuid_prog' to execute start commands
LSNRCTL for Solaris: Version 10.2.0.3.0 - Production on 27-FEB-2008 12:32:52
Copyright (c) 1991, 2006, Oracle. All rights reserved.
Starting /appl/oma-dm/oracle/product/10.2.0.3.64/bin/tnslsnr: please wait...
TNSLSNR for Solaris: Version 10.2.0.3.0 - Production
System parameter file is /var/opt/oracle/listener.ora
Log messages written to /appl/oma-dm/oracle/product/10.2.0.3.64/network/log/listener_omat.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=172.23.118.52)(PORT=1521)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=172.23.193.21)(PORT=1521)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=omaT)(PORT=1521)))
STATUS of the LISTENER
Alias LISTENER_OmaT
Version TNSLSNR for Solaris: Version 10.2.0.3.0 - Production
Start Date 27-FEB-2008 12:32:52
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /var/opt/oracle/listener.ora
Listener Log File /appl/oma-dm/oracle/product/10.2.0.3.64/network/log/listener_omat.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=172.23.118.52)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=172.23.193.21)(PORT=1521)))
Services Summary...
Service "OmaT" has 1 instance(s).
Instance "OmaT", status UNKNOWN, has 1 handler(s) for this service...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
Executing command: /opt/SUNWscor/oracle_listener/bin/oracle_listener_manage start
Feb 27 12:32:56 SC[SUNWscor.oracle_listener.start]:omadb-rg:omadb-listener: Listener LISTENER_OmaT started.
Feb 27 12:32:57 SC[SUNWscor.oracle_listener.monitor_start]:omadb-rg:omadb-listener: Starting monitor
Feb 27 12:33:28 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: The listener LISTENER_OmaT is not running; retry_count <3> exceeded. Attempting to switchover resource group.
Feb 27 12:33:28 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: retry_count <3> exceeded. NUM_RESOURCE_RESTART = 3
Feb 27 12:33:28 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: scha_control GIVEOVER failed with error code: 16
Feb 27 12:33:28 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: Attempting to restart listener LISTENER_OmaT.
Feb 27 12:33:28 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: scha_control RESOURCE_RESTART failed with error code: 16
Feb 27 12:33:58 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: The listener LISTENER_OmaT is not running; retry_count <3> exceeded. Attempting to switchover resource group.
Feb 27 12:33:58 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: retry_count <3> exceeded. NUM_RESOURCE_RESTART = 3
Feb 27 12:33:59 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: scha_control GIVEOVER failed with error code: 16
Feb 27 12:33:59 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: Attempting to restart listener LISTENER_OmaT.
Feb 27 12:33:59 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: scha_control RESOURCE_RESTART failed with error code: 16
Feb 27 12:34:29 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: The listener LISTENER_OmaT is not running; retry_count <3> exceeded. Attempting to switchover resource group.
Feb 27 12:34:29 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: retry_count <3> exceeded. NUM_RESOURCE_RESTART = 3
Feb 27 12:34:29 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: scha_control GIVEOVER failed with error code: 16
Feb 27 12:34:29 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: Attempting to restart listener LISTENER_OmaT.
Feb 27 12:34:29 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: scha_control RESOURCE_RESTART failed with error code: 16
Feb 27 12:35:00 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: The listener LISTENER_OmaT is not running; retry_count <3> exceeded. Attempting to switchover resource group.
Feb 27 12:35:00 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: retry_count <3> exceeded. NUM_RESOURCE_RESTART = 3
Feb 27 12:35:00 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: scha_control GIVEOVER failed with error code: 16
Feb 27 12:35:00 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: Attempting to restart listener LISTENER_OmaT.
Feb 27 12:35:00 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: scha_control RESOURCE_RESTART failed with error code: 16
Feb 27 12:35:30 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: The listener LISTENER_OmaT is not running; retry_count <3> exceeded. Attempting to switchover resource group.
Feb 27 12:35:30 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: retry_count <3> exceeded. NUM_RESOURCE_RESTART = 3
Feb 27 12:35:30 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: scha_control GIVEOVER failed with error code: 16
Feb 27 12:35:30 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: Attempting to restart listener LISTENER_OmaT.
Feb 27 12:35:30 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: scha_control RESOURCE_RESTART failed with error code: 16
Feb 27 12:36:01 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: Attempting to restart listener LISTENER_OmaT.
Feb 27 12:36:01 SC[SUNWscor.oracle_listener.monitor_stop]:omadb-rg:omadb-listener: Stopping fault monitor using pmfadm tag ORALSNR_MON_omadb-listener
Feb 27 12:36:03 SC[SUNWscor.oracle_listener.stop]:omadb-rg:omadb-listener: listener LISTENER_OmaT is not running.
Feb 27 12:36:04 SC[SUNWscor.oracle_listener.start]:omadb-rg:omadb-listener: Starting listener LISTENER_OmaT.
Feb 27 12:36:04 SC[SUNWscor.oracle_listener.start]:omadb-rg:omadb-listener: Using method 'run_setuid_prog' to execute start commands
LSNRCTL for Solaris: Version 10.2.0.3.0 - Production on 27-FEB-2008 12:36:04
Copyright (c) 1991, 2006, Oracle. All rights reserved.
Starting /appl/oma-dm/oracle/product/10.2.0.3.64/bin/tnslsnr: please wait...
TNSLSNR for Solaris: Version 10.2.0.3.0 - Production
System parameter file is /var/opt/oracle/listener.ora
Log messages written to /appl/oma-dm/oracle/product/10.2.0.3.64/network/log/listener_omat.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=172.23.118.52)(PORT=1521)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=172.23.193.21)(PORT=1521)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=omaT)(PORT=1521)))
STATUS of the LISTENER
Alias LISTENER_OmaT
Version TNSLSNR for Solaris: Version 10.2.0.3.0 - Production
Start Date 27-FEB-2008 12:36:04
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /var/opt/oracle/listener.ora
Listener Log File /appl/oma-dm/oracle/product/10.2.0.3.64/network/log/listener_omat.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=172.23.118.52)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=172.23.193.21)(PORT=1521)))
Services Summary...
Service "OmaT" has 1 instance(s).
Instance "OmaT", status UNKNOWN, has 1 handler(s) for this service...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
Executing command: /opt/SUNWscor/oracle_listener/bin/oracle_listener_manage start
Feb 27 12:36:08 SC[SUNWscor.oracle_listener.start]:omadb-rg:omadb-listener: Listener LISTENER_OmaT started.
Feb 27 12:36:09 SC[SUNWscor.oracle_listener.monitor_start]:omadb-rg:omadb-listener: Starting monitor
Feb 27 12:36:40 SC[SUNWscor.oracle_listener.monitor]:omadb-rg:omadb-listener: listener LISTENER_OmaT probe successful.
clrs show -v omadb-listener
=== Resources ===
Resource: omadb-listener
Type: SUNW.oracle_listener:5
Type_version: 5
Group: omadb-rg
R_description:
Resource_project_name: default
Enabled{sf2339}: True
Enabled{sf2340}: True
Monitored{sf2339}: True
Monitored{sf2340}: True
Resource_dependencies: omadb-stor
Resource_dependencies_weak: <NULL>
Resource_dependencies_restart: <NULL>
Resource_dependencies_offline_restart: <NULL>
--- Standard and extension properties ---
Probe_timeout: 180
Class: extension
Description: Timeout value (in seconds) used by monitor to check listener status.
Per-node: False
Type: int
User_env:
Class: extension
Description: File containing environment variables to be set before listener startup/shutdown
Per-node: False
Type: string
Listener_name: LISTENER_OmaT
Class: extension
Description: Oracle listener name
Per-node: False
Type: string
ORACLE_HOME: /appl/oma-dm/oracle/product/10.2.0.3.64
Class: extension
Description: Oracle Home diectory
Per-node: False
Type: string
Thorough_probe_interval: 30
Class: standard
Description: Time between invocations of a high-overhead fault probe of the resource.
Type: int
MONITOR_CHECK_TIMEOUT: 3600
Class: standard
Description: Maximum execution time allowed for Monitor_Check method.
Type: int
MONITOR_STOP_TIMEOUT: 120
Class: standard
Description: Maximum execution time allowed for Monitor_Stop method.
Type: int
MONITOR_START_TIMEOUT: 180
Class: standard
Description: Maximum execution time allowed for Monitor_Start method.
Type: int
BOOT_TIMEOUT: 30
Class: standard
Description: Maximum execution time allowed for Boot method.
Type: int
FINI_TIMEOUT: 30
Class: standard
Description: Maximum execution time allowed for Fini method.
Type: int
INIT_TIMEOUT: 30
Class: standard
Description: Maximum execution time allowed for Init method.
Type: int
UPDATE_TIMEOUT: 300
Class: standard
Description: Maximum execution time allowed for Update method.
Type: int
VALIDATE_TIMEOUT: 120
Class: standard
Description: Maximum execution time allowed for Validate method.
Type: int
STOP_TIMEOUT: 300
Class: standard
Description: Maximum execution time allowed for Stop method.
Type: int
START_TIMEOUT: 300
Class: standard
Description: Maximum execution time allowed for Start method.
Type: int
Retry_count: 3
Class: standard
Description: Indicates the number of times a monitor restarts the resource if it fails.
Type: int
Retry_interval: 300
Class: standard
Description: Time in which monitor attempts to restart a failed resource Retry_count times.
Type: int
Failover_mode: RESTART_ONLY
Class: standard
Description: Modifies recovery actions taken when the resource fails.
Type: enum

Oracle Resource Manager function with SAP BI7

Hi,
Have anyone considered or using Oracle Database Resource Manager (Oracle 10.2) feature for SAP BI application in your site? I dont see a single OSS hit on this feature.
We have a SAP BI system that has few power users (who can run large STAR_TRANSFORMATION queries that analyzes large volume of data) and the main user community (our sales force > 3000+ users) who can run smaller queries of such nature or queries of different types.
We want to see if there is any way we can control the resource utilization on the database server.
Thanks in advance,
Raj

> Of course, this would require an additional specifications such as SERVICE in the TNS and Listener files.
Yes - but I'm not sure if that would give the necessary effect. Once the statement reaches the database kernel engine, it gets processed, no matter if you limit the TNS/listener usage because TNS is no more involved when the statement reaches the OLAP engine.
> In the BI environment, I'm thinking you need this db feature to control database resources when loads and reports overlaps or even several small and large queries run concurrently despite however many app server a system has, all these come to the database.
I think SAPs answer is: Buy a bigger box (or use RAC to distribute the load)
> The big question is whether SAP would support such a setup.
The feature is not listed explicitly in note 105047 - Support for Oracle functions in the SAP environment. I'd make a call at BC-DB-ORA and ask what they think about that.
I understand your problem very well but I doubt, that there's an easy way of accomplishing this with standard tools.
Markus

Single or separate users owning multiple Oracle Resource Groups?

Being an infrastructure DBA, I have a question which I'm trying to sort out with my sys admin:
- We're trying to setup multiple Oracle 11g (non-RAC) instances on a two-node Solaris 10 cluster.
- each 'database' would have its own resource group, filesystem, binaries, and listener
- In order to fully separate the two instances, the SA actually gave us two different oracle accounts to control each resource group.
ie. a different oracle user (ie. oracle1, oracle2, oracle3) owns each resource group (/rg1, /rg2, /rg3)
- to patch/startup/shutdown each instance, we have to login as a separate user
- no user can run/touch the other's files (they're in completely different groups (dba/oinstall, dba2/oinstal2, dba3/oinstal3)
- to run patch/installing, we use a separate inventorypointer flag which points to that particular db's oraInventory (ie. ./runInstaller -invPtrLoc /var/opt/oracle/oraInst.loc.<resource_group_name>)
I asked why couldn't one user own all resource groups, and was told:
...Oracle uses the shared memory, semaphores and queues to exchange information. Each IPC object has an identifier and access information, similar to files (owner, ,group, mode). If you use the single oracle account in different RGs, you or system might accidentally destroy the IPC object which belongs to other Resource Group.
Is this true? I could have sworn I've seen other solaris setups (albeit with Veritas Resource Groups) setups which have multiple resource groups owned/managed by a single oracle user, but I don't know enough about semaphores and shared memory to truly understand his argument.
The way I was hoping to work would be:
- a single oracle user owning several resource groups
- each resource group mapping to a filesystem tree, ie:
     /home
          /oracle
     /rg1
          /opt
               /oracle
     /rg2
          /opt
               /oracle
     /rg3
          /opt
               /oracle- shared /var/opt/oracle/oratab
- to switch between instances, the oracle user simply does the same '. oraenv' command as regular.
I understand it can be done, just that I need something to counter my SA's argument that there would be potential IPC/shared memory/semaphore collisions.

I've marked the question as answered, to a degree: I can agree that there are successful implementations out there with one person running multiple solaris zones, I just couldn't explain it to the SA in an articulate manner. I've gone to Oracle Metalink with a service request and will post references to the notes that the support person gave me on the subject. It's good for research in this area:
Note 15654.1 TECH: Calculating Oracle's SEMAPHORE Requirements
Note 70688.1 Location and Display of kernel parameters - Solaris
Note 33244.1 SOLARIS: Shared Memory and Semaphore Kernel Parameters on Solaris (SPARC) Servers
Note 153961.1 Semaphores and Shared Memory - An Overview
We've ruled out local zones at the time, for other implementation reasons. What I think we're looking at is the trade-off between Sysadmin's management complexity (separate zones) and DB Admin's management complexity (separate users).

Enable a disabled user on the native oracle resource

I have to enable a disabled account on the native resource from a form.
Field name='view.accounts[$(Resource)].enable'
doesnot work whereas
Field name='view.accounts[$(Resource)].disable'
works properly. I have a custom adapter which has the required "SupportsAccountDisable( )" method returns a true value for both enable and disable to work as per the IdM documentation.
Please help.

This is an AccessManager related forum. I�m afraid that you won�t get an answer for Identity Manager.
-Bernhard

Help: Policy Server consuming Oracle resources with ANALYZE operations

Dear all,
we have a problem with APS 7.0.2 on Win 2003 server R2 that uses an Oracle instance on HP-UX (but I suppose the problem is not related to the specific operating systems).
Apparently, Policy Server periodically produces queries Oracle for statistics but the generated load is so high that the database cannot work for some time and sometimes it is necessary to stop Policy Server and/or the database daemon.
Is it possible to disable statistics collection?
How?
Anybody has the same problem?

Hi,
UNC file pathnames (for ex (\\host-machine\asdf) )are no longer supported by JRE 1.6.0.24+
Solution
There are two workarounds at this moment:
1. You may use JRE v 1.6.0_23
2. Update the path to a physical address (for example
C:\Ora10gMID\Apache\Apache\htdocs\repcache) or URL (for example,
@ http://njwin20-v02.us.oracle.com:7779/repcache/) when creating the document record.
Regards,
Kal

ORACLE RESOURCE MANAGER - POOR RESULTS

Hi all.
Created a smple test case - basically consumed FULL server CPU with queiing by generic user.
Then came in with a user who has 40% allocaiton at P1.
here are the basic results
NO LOAD (server idle) => 7 secs
100% LOAD (user in TOP CPU group -> 40% at P1) => 35 secs
100% LOAD (user in TOP CPU group -> 50% only at P5) => 90 secs
So - on a basic level - ORM works to prevent queries going from 7 secs to 90 secs.
But from an SLA perspective the business isn't going to be too happy if it still goes from 7 to 34 secs ??
thoughts ?

bump

Oracle resource manager10.2.0.4/11.2.0.2

Similar Messages

Maybe you are looking for