Start a job upon database startup

Hi,
I have created a job which I would like to run on database startup. What is the best way to do this. I tried using "after startup on database" but could not get it to work.
What is the best way to make sure a job gets scheduled as soon as the database startsup.
thanks for the help

Hi,
There is no documented way of using the Scheduler to do this and the "after startup on database" trigger sounds like the right thing to do. Why doesn't it work ?
One thing which might work is creating a one-time job in the trigger to run immediately (if you use dbms_scheduler.create_job it must be in an autonomous transaction) . Or having the job exist but calling run_job from the trigger (with use_current_session=>false) - this would also have to be in an autonomous txn.
If you are having trouble getting the trigger to work you might need to post on the general database forum.
Hope this helps,
Ravi.

Similar Messages

Start Workflow from the After startup database trigger

Hallo,
I try to startup a workflow process from a database trigger :
the after startup database trigger. But when I do this, he
doesn't startup. When I add a commit-statement after the call
to startup the workflow, my database never gets open.
What do I have to do ? And what command is used ?
Thanks a lot.
Filip Huysmans.

See the Posting: Starting Workflows From a Database Trigger
Hallo,
I try to startup a workflow process from a database trigger :
the after startup database trigger. But when I do this, he
doesn't startup. When I add a commit-statement after the call
to startup the workflow, my database never gets open.
What do I have to do ? And what command is used ?
Thanks a lot.
Filip Huysmans.

"can not start a job" issue in AWM

Hi ALL,
I am maintaining my cube from PLSQL with following options
1. buildtype = "BACKGROUND"
2. trackstatus = "true"
3. maxjobqueues = 3
i get following error when i see the "olapsys.xml_load_log" table
***Error Occured: Failed to Build(Refresh) DB_OWNER.MY_ANALYTICAL_WORKSPACE Analytic Workspace. Can not start a job.
Can anybody explain when and why this error occurs? I have wasted a lot of time searching for this issue, but have found no person facing such issue.
Hi Keith, it will be great if you can answer this one.
My database version is 10.2.0.4.0 and AWM version is also 10.2.0.3.0
Kind Regards,
QQ
Message was edited by:
dwh_10g

Applies to:
Oracle OLAP - Version: 10.1 to 11.1
This problem can occur on any platform.
Symptoms
- We have an AW maintenance / refresh script or procedure that contains BuildType="BACKGROUND", so that the AW maintenance task will be sent to the Oracle Job queue.
- When we execute the AW maintenance / refresh script or procedure, we do not get any errors in the foreground, the script/procedure has been executed successfully.
- However when we look into the build/refresh log (see <Note 351688.1> for details) we see that the maintenance/refresh task failed with:
13:29:39 Failed to Submit a Job to Build(Refresh) Analytic Workspace <schema>.<AW Name>.
13:29:39 ***Error Occured in BUILD_DRIVER
- In the generated SQL trace for the session of the user who launches the AW build/refresh script or procedure, we see that ORA-27486 insufficient privileges error occurred at creation of the job.
We see from the relevant bit of the SQL trace that err=27486 occured while executing the #20 statement which is 'begin DBMS_SCHEDULER.CREATE_JOB ...', and the statement is parsed and tried to be executed as user having uid=91:
PARSING IN CURSOR #20 len=118 dep=2 uid=91 oct=47 lid=91 tim=1176987702199571
hv=1976722458 ad='76dd8bcc'
begin
DBMS_SCHEDULER.CREATE_JOB(:1, 'plsql_block', :2, 0, null, null, null,
'DEFAULT_JOB_CLASS', true, true, :3); end;
END OF STMT
PARSE
#20:c=1000,e=1100,p=0,cr=0,cu=0,mis=1,r=0,dep=2,og=1,tim=1176987702199561
EXEC #20:c=65990,e=125465,p=10,cr=1090,cu=3,mis=1,r=0,dep=2,og=1,tim=
1176987702325167
ERROR #20:err=27486 tim=465202984
Cause
User who tries to create a job (executes DBMS_SCHEDULER.CREATE_JOB() procedure) does not have the sufficient privileges.
Solution
1. Identify the user under which the job is supposed to be created. This user is not necessarily the same as the user who launched AW build/refresh script or procedure. Get the corresponding username from one of the %_USERS views e.g. from ALL_USERS.
e.g.
SELECT user_id,username FROM all_users WHERE user_id=91;
2. Identify the system privileges currently assigned to the user by connecting as the user whom the privileges need to be determined, and execute:
SELECT * FROM SESSION_PRIVS ORDER BY PRIVILEGE;
3. Ensure that the CREATE JOB privilege is listed.
The CREATE JOB privilege can be granted in various ways to a user:
- via role OLAP_USER or via role OLAP_DBA (see view ROLE_SYS_PRIVS for what privs are assigned to a role):
GRANT OLAP_USER TO <username>;
- explicitly
GRANT CREATE JOB TO <username>;

Error saving job to database for standard jobs scheduling

Hi,
In IDES server when iam goto Tr.code -- SM36 -- Standard Jobs -- Default Scheduling iam getting below error.
Error saving job to database
Message no. BT117
Diagnosis
The SAP system was unable to save the current job in the database. This failure suggests that there is a problem with the database system or with the network connections between the SAP application servers and the database system.
System Response
Job not saved and not scheduled.
Procedure
To analyze this problem, start by checking the system log for messages about network or database problems. You can also use the computing center management system to check your system for problems.
Guide me for the same.
Thanku

HI,
Sometimes this error will come.
Try to schedule jobs manually using SM36 instead of using standard job button.
Also you can check this thread
Re: Error saving job SAP_REORG_JOBS to database
Which seems to report same problem.
Its nothing to take with database conenctivity as SAP is up and running .
Try this and revert.
Regards,

Personal Oracle 8i Database startup password

Can someone provide the database startup password for Personal Oracle 8i.I have tried passwords like "oracle","sys","manager"in both uppercase and lowercase.
None of this works.I have read the required documentation for the same.But I haven't recd any information.
Thanks.

Hi,
Normally this combination should work.
Anyway, try this out.
In the command prompt,
set ORACLE_SID=<sid name>
start server manager/svrmgrl
connect internal.
At this juncture , if you are getting errors, exit the svrmgr application.
try to reset the password for internal with a new password file. (Backup the old one).
Tr connecting.
Regards
Lakshmanan, K

How to stop and start listener auto. when database is open and shutdown?

Hi,
is there a way, in Window , i can shutdown the listener service when the database is shutdown (the rdbms service still up) and startup the listener when the database is open?
Thanks

Ron_B wrote:
In simple way,
when the window rdbms service is runing and the database is in shutdown or stop state, the listener have to be stop.
The listener have to be start only when the database pass from nomount to mount.With mentioning the fact that there is abosultely no such dependency between listener and database, I am really curious to know that why you want to do it? Listener is merely a process and even if its running, there is no such harm or resource consumption it would do that you need to shut it down as and when db would be.
HTH
Aman....

Database startup error message

Hi Guys,
When I startup my Database, I always see this error message printed in the trace file:
Error in executing triggers on database startup
*** 2005-12-09 11:12:42.817
ksedmp: internal or fatal error
ORA-00604: error occurred at recursive SQL level 1
ORA-12663: Services required by client not available on the server
ORA-36961: Oracle OLAP is not available.
ORA-06512: at "SYS.OLAPIHISTORYRETENTION", line 1
ORA-06512: at line 15
Error in executing triggers on database startup
*** 2005-12-09 11:12:42.869
ksedmp: internal or fatal error
ORA-00604: error occurred at recursive SQL level 1
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at line 4
I have a few questions about the above message:
1. How can I see which database startup trigger is having this error? Is there a way to determine that?
2. Is there a way I can disable all triggers that fire on database startup? (just like we can disable triggers on a table)
3. Any idea what ORA-36961: Oracle OLAP is not available. means?
Thanks

hey..thanks for the reply, I have checked to see if any triggers are enabled on startup from the USER_TRIGGERS
SQL> select TRIGGER_NAME from DBA_TRIGGERS where TRIGGERING_EVENT='STARTUP';
no rows selected
SQL>
But when I start my database, I again see this error message:
Error in executing triggers on database startup
*** 2005-12-12 05:32:40.778
ksedmp: internal or fatal error
ORA-00604: error occurred at recursive SQL level 1
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at line 4
Is there any way I can check what trigger Oracle is complaining about?
Also, how can I disable OLAP so that I don't see the OLAP error message?
Thanks

Can not start instance SAP - ABAP Database is not available via R3trans

Dear all !
My OS : Linux RHEL 4U7 32bit
Oracle 10G R2 32bit 10.2.0.2
when system running but power off suddenly
and when power on ->
i am having problem as below when i start instance SAP (Databse Oracle Started)
Step 1 : I login user (ora<sid>) of Oracel to start up database
Database startup -> OK
then i tried to shutdown database -> OK too
and start up again -> OK
Query -> OK
I think Database do not problem
Step 2: start listener -> OK
Step 3: i login user (<sid>adm) and startup instance SAP (command : startsap r3) with error:
Checking SED Database
ABAP Database is not available via R3trans
Starting SAP-Collector Daemon
11:11:48 10.02.2010   LOG: Effective User Id is root
This is Saposcol Version COLL 20.90 700 - Intel x86 with Linux, PL:75, Aug 29 2006
Usage: saposcol -l: Start OS Collector
        saposcol -k: Stop OS Collector
        saposcol -d: OS Collector Dialog Mode
        saposcol -s: OS Collector Status
The OS Collector (PID 6870) is already running .....
saposcol already running
ABAP Database SED must be started first
Please help me to resolve this problem
Thanks for your advice

Dear all !
1. output of tnsping SED :
TNS Ping Utility for Linux: Version 10.2.0.2.0 - Production on 11-FEB-2010 13:51:24
Copyright (c) 1997, 2005, Oracle. All rights reserved.
Used parameter files:
/oracle/SED/102_32/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (COMMUNITY = SAP.WORLD)(PROTOCOL = TCP)(HOST = sapsed)(PORT = 1527))) (CONNECT_DATA = (SID = SED) (GLOBAL_NAME = SED.WORLD)))
OK (0 msec)
2. output startsap_.log
Checking SED Database
ABAP Database is not available via R3trans
Starting SAP-Collector Daemon
saposcol already running
ABAP Database SED must be started first
---> output above repeats many
3. output trans.log
4 ETW000 R3trans version 6.14 (release 700 - 18.09.06 - 09:35:00).
4 ETW000 unicode enabled version
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time   : 11.02.2010 - 13:49:36
4 ETW000 control file: <no ctrlfile>
4 ETW000 R3trans was called as follows: R3trans -d
4 ETW000 trace at level 2 opened for a given file pointer
4 ETW000 [dev trc     ,00000] Thu Feb 11 13:49:36 2010                             159 0.000159
4 ETW000 [dev trc     ,00000] db_con_init called                                    27 0.000186
4 ETW000 [dev trc     ,00000] create_con (con_name=R/3)                             55 0.000241
4 ETW000 [dev trc     ,00000] Loading DB library '/usr/sap/SED/SYS/exe/run/dboraslib.so' ...
4 ETW000                                                                              63 0.000304
4 ETW000 [dev trc     ,00000] load shared library (/usr/sap/SED/SYS/exe/run/dboraslib.so), hdl 0
4 ETW000                                                                           16430 0.016734
4 ETW000 [dev trc     ,00000] Library '/usr/sap/SED/SYS/exe/run/dboraslib.so' loaded
4 ETW000                                                                              56 0.016790
4 ETW000 [dev trc     ,00000] function DbSlExpFuns loaded from library /usr/sap/SED/SYS/exe/run/dboraslib.so
4 ETW000                                                                              41 0.016831
4 ETW000 [dev trc     ,00000] Version of '/usr/sap/SED/SYS/exe/run/dboraslib.so' is "700.08", patchlevel (0.73)
4 ETW000                                                                              94 0.016925
4 ETW000 [dev trc     ,00000] function dsql_db_init loaded from library /usr/sap/SED/SYS/exe/run/dboraslib.so
4 ETW000                                                                              38 0.016963
4 ETW000 [dev trc     ,00000] function dbdd_exp_funs loaded from library /usr/sap/SED/SYS/exe/run/dboraslib.so
4 ETW000                                                                              68 0.017031
4 ETW000 [dev trc     ,00000] New connection 0 created                              44 0.017075
4 ETW000 [dev trc     ,00000] 0: name = R/3, con_id = -000000001 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000                                                                              46 0.017121
4 ETW000 [dev trc     ,00000] db_con_connect (con_name=R/3)                         38 0.017159
4 ETW000 [dev trc     ,00000] find_con_by_name found the following connection for reuse:
4 ETW000                                                                              37 0.017196
4 ETW000 [dev trc     ,00000] 0: name = R/3, con_id = 000000000 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000                                                                              39 0.017235
4 ETW000 [dev trc     ,00000] Oracle Client Version: '10.2.0.2.0'                  480 0.017715
4 ETW000 [dev trc     ,00000] -->oci_initialize (con_hdl=0)                         42 0.017757
4 ETW000 [dev trc     ,00000] Client NLS settings: AMERICAN_AMERICA.UTF8          3789 0.021546
4 ETW000 [dev trc     ,00000] Logon as OPS$-user to get SAPSR3's password           48 0.021594
4 ETW000 [dev trc     ,00000] Connecting as /@SED on connection 0 (nls_hdl 0) ... (dbsl 700 110706)
4 ETW000                                                                              51 0.021645
4 ETW000 [dev trc     ,00000] Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
4 ETW000                                                                              43 0.021688
4 ETW000 [dev trc     ,00000]    0 UTF8                                                      1 0x9511ea0 0x951750c 0x9516d94
4 ETW000                                                                              40 0.021728
4 ETW000 [dev trc     ,00000] Allocating service context handle for con_hdl=0       40 0.021768
4 ETW000 [dev trc     ,00000] Allocating server context handle                      52 0.021820
4 ETW000 [dev trc     ,00000] Attaching to DB Server SED (con_hdl=0,svchp=0x9516d20,svrhp=0x9528504)
4 ETW000                                                                              88 0.021908
4 ETW000 [dboci.c     ,00000] *** ERROR => OCI-call 'OCIServerAttach' failed: rc = 12505
4 ETW000                                                                            4712 0.026620
4 ETW000 [dbsloci.    ,00000] *** ERROR => CONNECT failed with sql error '12505'
4 ETW000                                                                              49 0.026669
4 ETW000 [dev trc     ,00000] Try to connect with default password                  62 0.026731
4 ETW000 [dev trc     ,00000] Connecting as SAPSR3/<pwd>@SED on connection 0 (nls_hdl 0) ... (dbsl 700 110706)
4 ETW000                                                                              39 0.026770
4 ETW000 [dev trc     ,00000] Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
4 ETW000                                                                              56 0.026826
4 ETW000 [dev trc     ,00000]    0 UTF8                                                      1 0x9511ea0 0x951750c 0x9516d94
4 ETW000                                                                              47 0.026873
4 ETW000 [dev trc     ,00000] server_detach(con_hdl=0,stale=0,svrhp=0x9528504)
4 ETW000                                                                              37 0.026910
4 ETW000 [dev trc     ,00000] Detaching from DB Server (con_hdl=0,svchp=0x9516d20,srvhp=0x9528504)
4 ETW000                                                                              37 0.026947
4 ETW000 [dev trc     ,00000] Deallocating server context handle 0x9528504          45 0.026992
4 ETW000 [dev trc     ,00000] Allocating server context handle                      48 0.027040
4 ETW000 [dev trc     ,00000] Attaching to DB Server SED (con_hdl=0,svchp=0x9516d20,svrhp=0x9528504)
4 ETW000                                                                              60 0.027100
4 ETW000 [dboci.c     ,00000] *** ERROR => OCI-call 'OCIServerAttach' failed: rc = 12505
4 ETW000                                                                            1538 0.028638
4 ETW000 [dbsloci.    ,00000] *** ERROR => CONNECT failed with sql error '12505'
4 ETW000                                                                              41 0.028679
4 ETW000 [dblink      ,00431] ***LOG BY2=>sql error 12505 performing CON [dblink#3 @ 431]
4 ETW000                                                                             131 0.028810
4 ETW000 [dblink      ,00431] ***LOG BY0=>ORA-12505: TNS:listener does not currently know of SID given in connect descriptor [dblink#3 @ 431]
4 ETW000                                                                              39 0.028849
2EETW169 no connect possible: "DBMS = ORACLE                           --- dbs_ora_tnsname = 'SED'"
thansk for your help
Edited by: myfriend280985 on Feb 11, 2010 7:53 AM

Issue with database startup

hi,
getting below error on database startup.
log is attached from alert log file.
Wed Nov 16 14:24:20 2011
ALTER DATABASE MOUNT
Wed Nov 16 14:24:20 2011
ORA-00202: control file: '/oradata2/ctftdb2/data/controlctftdb201.ctl'
ORA-27086: unable to lock file - already in use
SVR4 Error: 11: Resource temporarily unavailable
Additional information: 8
Additional information: 5457
Wed Nov 16 14:24:20 2011
ORA-205 signalled during: ALTER DATABASE MOUNT...

user12052679 wrote:
SID is ctftdb2
bash-3.00$ ps -ef | grep pmon
oracle 5992 1 0 14:24:19 ? 0:07 ora_pmon_ctftdb2
oracle 1680 1 0 May 25 ? 193:47 ora_pmon_hddb
oracle 5445 1 0 Jul 19 ? 287:57 ora_pmon_ctftdb2
oracle 14334 28506 0 16:28:22 pts/3 0:00 grep pmonyour instance is already up, why trying to start again? are you not aware as it is already running?
First shutdown the current instance which you facing errors to mount database
export ORACLE_SID=ctftdb2
sqlplus / as sysdba
select name,open_mode from v$database;Might it is already either mounted or opened. post output here

When the Database startup and open? please please not alert log

Hello all
is there is a script or dinamic view which query what time the database startup and shutdown.
please don't answer me with opent alert log, am looking for view or script only
thank you
regards

You wrote you don't want to use the alert.log. But
still this could provide all the information you want
to have.
If you dont want to use the alert.log because you
need to query the information by using sql you may
consider to access the alert.log via a external table.Even the alert log may not meet the new requirements of 'all startup and shutdown history'. In a typical shop, the alert log is periodically archived or wiped.
The answer to the OPs question probably lies in creating a new table to store the v$instance information, and create a database startup and possibly a database shutdown trigger to fill that table.
Or start using Grid Control which has that information tucked away in one of the internal sysman tables.

Windows 7 x64 only installs the drivers for USB devices that are plugged in upon system startup

Hi all,
I have a most unusual problem. On my personal desktop, I can only use USB devices that are plugged in upon system startup. If I unplug a USB device and then plug it in again, the driver will not install correctly. I cannot force the device to start and I
can't pick a driver manually. All I get is this. If I plug in a USB device and then reboot, the driver gets installed correctly and I can use it until I unplug it again. I'm pretty sure it's a Windows issue
but I can list the hardware I have if it is needed.
I have tried:
Running an SFC /SCANNOW as administrator
Uninstalling all USB controllers via device manager and letting them reinstall
Neither worked to resolve the issue. If this was a client's computer I would probably just reinstall Windows but because this is my main work PC it'd be a huge hassle to do it, so I'd really appreciate any other ideas anyone has. If I have to reinstall I
will. Thanks!

Hi,
Since the issue just happened for 4 monthes, I consider that some changes or updates may cause the issue.
Please also try to restore the system back to the point before this issue.
You can also try these steps:
1.Power down your laptop or desktop
2.Physically unplug the computer. If it’s a laptop, remove the battery too.
3.Leave it disconnected for three minutes
4.Replug the desktop or reinsert the battery
5.Power on the system
For the reasons, you can refer to this article:
How to fix “USB device not recognized”
http://www.fixedbyvonnie.com/2013/10/how-to-fix-usb-device-not-recognized/#.UvtCLf7xvwo
Kate Li
TechNet Community Support

Error saving job to database

Hi,
In IDES ECC6.0 Ehp 3 (Os: window 2003 64bit DB: oracle 10.2.0.2) server when iam goto T-Code -- SM36 -- Standard Jobs -- Default Scheduling iam getting below error.
<error saving job to database>
So I patched oracle 10.2.0.1 to 10.2.0.4, and kernel patch with latest one.
But, the same error occured.
I tried to execute r3trans -d at the OS level,the results is <The system cannot execute the specified program>.
In SM21, i am getting below error
<error saving job to database>
&CAUSE &
The SAP system was unable to save the current job in the database. This failure suggests that there is a problem with the database system or with the network connections between the SAP application servers and the database system.
&SYSTEM_RESPONSE&
Job not saved and not scheduled.
&What_TO_DO&
To analyze this problem, start by checking the <DS:TRAN.SM21>system log for message about network or database problems. you can also use the <DS:TRAN.SRZL>computing center management system to check your system for problems. >
I checked SM28 and SICK and it reports no error.
Please help how can I schedule the standard jobs

Make sure you use the proper kernel, for 64bit there are two kernels:
- one for AMD64 and Intel64
- one for Itanium-2 64bit
The R3trans seems to be the wrong one - as I would suggest are the brtools.
Markus

Message bean does not start automatically during application server startup

I have a message bean that does not start up during application server startup. I am able to successfully start the application manually using the visual admin tool.I searched the logs and found the following error. The error references the "QueueConnectionFactory" is not deployed or is not started. I have check and the "QueueConnectiopnFactory" is deployed. Is this a problem with the application trying to start before the "QueueConnectionFactory"? Is thier a way to define a dependency on my application not to start until the "QueueConnectionFactory" has been started, if so can how would I define this dependency. Please provide and example.
Thanks,
Bill
#1.5 #001CC4695AD8001A000000100000079C00045DB6C93D4DAD#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Connecting Model Repository ...#
#1.5 #001CC4695AD8001A000000110000079C00045DB6C93D4E1D#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Checking source path: halliburton.com/hal~usrgrpap#
#1.5 #001CC4695AD8001A000000120000079C00045DB6C93D4EAC#1228939548538#System.err##System.err#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Error##Plain###[RunTask] The source file/path doesn't exist: halliburton.com/hal~usrgrpap#
#1.5 #001CC4695AD8001A000000130000079C00045DB6C93D4EF5#1228939548538#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Opening connection to MMR ...#
#1.5 #001CC4695AD8001A000000140000079C00045DB6C93D69D0#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Start local transaction ...#
#1.5 #001CC4695AD8001A000000150000079C00045DB6C93D6B5A#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Commit ...#
#1.5 #001CC4695AD8001A000000160000079C00045DB6C93D6C8B#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Running task 'com.sap.ip.mmr.db.tasks.TaskUndeployFromDB' ...#
#1.5 #001CC4695AD8001A000000170000079C00045DB6C93D8E6C#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###Close connection to Model Repository ...#
#1.5 #001CC4695AD8001A000000180000079C00045DB6C93D8EE5#1228939548553#com.sap.ip.mmr.tools.RunTask##com.sap.ip.mmr.tools.RunTask#Administrator#79423####d7c673d0c6f411dd92de001cc4695ad8#SAPEngine_Application_Thread[impl:3]_33##0#0#Info##Plain###done.#
#1.5 #001CC4695AD80018000000000000171400045DBBE9BCCED0#1228961568691#com.sap.engine.services.connector##com.sap.engine.services.connector######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error##Plain###ResourceObjectFactory.getObjectInstance(), Error: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
#1.5 #001CC4695AD80018000000010000171400045DBBE9BCE3CD#1228961568691#com.sap.engine.services.jndi##com.sap.engine.services.jndi######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Warning#1#/System/Audit#Java###Exception #1#com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                ... 24 more
#1.5 #001CC4695AD80018000000030000171400045DBBE9BDBF4A#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#deploy_5029##Exception in operation startApp with application halliburton.com/halusrgrpap.#2#startApp#halliburton.com/halusrgrpap#
#1.5 #001CC4695AD80018000000040000171400045DBBE9BDC46C#1228961568753#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception in operation startApp with application halliburton.com/hal~usrgrpap.
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:394)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:367)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                ... 12 more
Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                ... 16 more
Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                ... 19 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                ... 20 more
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                ... 24 more
#1.5 #001CC4695AD80018000000060000171400045DBBE9BE0AF5#1228961568769#com.sap.engine.services.deploy##com.sap.engine.services.deploy######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Plain###
Operation startApp over application halliburton.com/hal~usrgrpap finished with errors on server 105677750. For more detailed information see traces of Deploy Service.#
#1.5 #001CC4695AD80018000000080000171400045DBBE9BE27D1#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Server#Java#ejb_2119##Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.#1#com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP#
#1.5 #001CC4695AD80018000000090000171400045DBBE9BE2842#1228961568769#com.sap.engine.services.ejb##com.sap.engine.services.ejb######27cee540c72911ddb4ee001cc4695ad8#SAPEngine_System_Thread[impl:5]_25##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.halliburton.esg.eas.sec.prtusrgrpprocessing.MDBPrtUsrGrpProcBean0_0ContainerFP.
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1013)
                at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2443)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
                at com.sap.engine.services.deploy.server.application.StartTransaction.prepareLocal(StartTransaction.java:176)
                at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:365)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
                at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4450)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2610)
                at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2464)
                at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144)
                at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19)
                at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102)
                at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
                at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
                at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:451)
                at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:153)
                at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)
                at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:1007)
                ... 16 more
Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name PortalUserGroupProcessingQueue not found in the naming.
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:129)
                at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:449)
                ... 19 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/halliburton.com/hal~usrgrpap/QueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.]
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:529)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at javax.naming.InitialContext.lookup(InitialContext.java:347)
                at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:115)
                ... 20 more
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "QueueConnectionFactory" does not exist. Possible reasons: the connector in which ConnectionFactory "QueueConnectionFactory" is defined is not deployed or not started.
                at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:72)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:31)
                at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:210)
                at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:280)
                at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:414)
                ... 24 more
#1.5 #001CC4695AD80019000000000000171400045DBBEB38B908#1228961593581#com.sap.jpe.engine.impl.common.AnalyzerModel#sap.com/com.sapportals.supportplatform#com.sap.jpe.engine.impl.common.AnalyzerModel#Administrator#67####43c8e9d0c72911ddcedd001cc4695ad8#SAPEngine_Application_Thread[impl:3]_38##0#0#Error##Plain###Exception while loading class: com.sapportals.supportplatform.plugins.portal.connectors.ConnectorGatewayServiceCheck
java.lang.NoClassDefFoundError: com/sapportals/portal/prt/resource/ResourceException
                at java.lang.Class.getDeclaredConstructors0(Native Method)
                at java.lang.Class.privateGetDeclaredConstructors(Class.java:1618)
                at java.lang.Class.getConstructor0(Class.java:1930)
                at java.lang.Class.newInstance0(Class.java:278)
                at java.lang.Class.newInstance(Class.java:261)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadClass(PluginCollector.java:881)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:387)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.getPluginDescFromXMLFile(PluginCollector.java:274)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadPluginsFromJarFile(PluginCollector.java:169)
                at com.sap.jpe.engine.impl.pluginloading.PluginCollector.loadFromExtDirectory(PluginCollector.java:121)
                at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:411)
                at com.sap.jpe.engine.impl.common.AnalyzerModel.loadPlugins(AnalyzerModel.java:399)
                at com.sapportals.supportplatform.SupportPlatform.init(SupportPlatform.java:81)
                at com.sap.engine.services.servlets_jsp.server.security.PrivilegedActionImpl.run(PrivilegedActionImpl.java:59)
                at java.security.AccessController.doPrivileged(Native Method)
                at javax.security.auth.Subject.doAs(Subject.java:379)
                at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:141)
                at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
                at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
                at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                at java.security.AccessController.doPrivileged(Native Method)
                at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

I though the same thing, but XE LISTENER is running on localhost and port 1522. On the other hand XE have local_listener explicitly set to the very same connection descriptor. Even XE installation was second on this server.
I've could change that yes, but the startup script doesn't seemed to have this mind.
Regards,
Sve

Error starting batch job through Data Services Web Service

I have a customer running our web service interface to BODS. We have not been able to successfully start any jobs due to the following error:
Services sent the request to start batch job 'Job_Test_Web_Services' on server 'null'. The Job Server refused the request with error: Job Server not found
The same interface works against other environments (all XI 3.1), so I need some pointers as to where it gets the server name. Sounds to me like a configuration issue, but I am not a BO DS admin and don't know where to look.
Please help.
Thanks.

I was able to reproduce this issue in our own lab by going to the BO DS Server Manager and removing the servers from the configuration. Not sure if this is what is happening at this customer site, but I will check it out and post back.
Not sure why they would not have a Job Server defined if they want to run jobs!

How to Schedule Job using Database Control for SQLPLUS script?

Hi All,
I am using Database version 10.2. I would like to schedule a SQLPLUS script job using Database control (Not using Grid Control!). The following is the script.
========================================================
define OEM_FRIENDLY=1
define OWB_BACKGROUND=0
set serveroutput on
set verify off
whenever sqlerror exit failure;
define REPOS_OWNER='&1.'
define LOCATION_NAME='&2.'
define TASK_TYPE='&3.'
define TASK_NAME='&4.'
define SYSTEM_PARAMS='&5.'
define CUSTOM_PARAMS='&6.'
alter session set current_schema = &REPOS_OWNER.;
set role owb_d_&REPOS_OWNER., owb_o_&REPOS_OWNER.;
variable exec_return_code number;
begin
-- Initialize Return Code
:exec_return_code := wb_rt_api_exec.RESULT_FAILURE;
-- Run Task
:exec_return_code := wb_rt_api_exec.run_task('&LOCATION_NAME.',
'&TASK_TYPE.',
'&TASK_NAME.',
'&CUSTOM_PARAMS.',
'&SYSTEM_PARAMS.',
&OEM_FRIENDLY.,
&OWB_BACKGROUND.);
end;
exit :exec_return_code;
===========================================================
Is it possible to schedule SQLPLUS script with 6 different parameters? If yes then how can I schedule for monday to friday or only for Saturday and sundays.
Please provide brief steps.
Thanks for your help in advance.
- Mehul

Let me explain to you about scheduler.
You can schedule a pl/sql stored procedure TEST_S as follows...
Begin
dbms_scheduler.create_job(
job_name=>'MY_JOB',
Job_Type=>'STORED_PROCEDURE',
job_action=>'TEST_S',
start_date=>sysdate,
repeat_interval=>'freq=monthly;BYDAY=MON,TUE,WED,THU,FRI',
end_date=>null');
END;
You can also also execute o/s script like .bat or .sh. For this job type should be EXECUTABLE.
Example of converting a .sql script in .bat script...
insert.sql
insert into dept values(50,'IT','LONDON');
exit
insert.bat
sqlplus scott/tiger @insert.sql
Executing now...
C:\Documents and Settings>insert.bat
C:\Documents and Settings>sqlplus scott/tiger @insert.sql
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Mar 1 08:01:00 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
1 row created.
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - P
oduction
With the Partitioning, OLAP and Data Mining options
C:\Documents and Settings>
So first read about DBMS_SCHEDULER and do the work in prompt. Then you can go and schedule it even by database control.
Scheduling by database control...
http://www.oracle.com/technology/oramag/oracle/04-jul/o44tech_dba.html
Scheduler
http://download-uk.oracle.com/docs/cd/B19306_01/appdev.102/b14258/d_sched.htm#CIHEHDHA
PS: By default each job you created is disable state. Please enable it by enable procedure of DBMS_SCHEDULER package.

Start a job upon database startup

Similar Messages

Maybe you are looking for