Bakground job failed with error EXSQL UNKNOWN CONNECTION

Hello,
We are scheduling job is background which connects to other system and picks up entries to update it.
The report works very well in foreground no error, no dumps, no connectivity issues.
When report is schedule in background it gives dumps throwing error 'EXSQL UNKNOWN CONNECTION' which is near the DISCONNECT statement.
All authorisation and everything is in place as job runs in foreground and also in background sometimes.
Please help.

Hi Sunny,
Yes I have analysed the dumps in st22.
We have scheduled the background jobs which are exchanging data with external databases.
Sometimes these background jobs get finished and sometimes it gets cancelled and gives the above mentioned ABAP dumps.
I am not sure whether it is related to the database connectivity or something else?
Waiting for the response.
Thanks & Regards,
Prem

Similar Messages

  • OIM - Reconciliation jobs fail with Error: OPERATIONS_ERROR

    Hi,
    after integrating OIM with OAM for Fusion Apps provisioning (11.1.3), LDAP Reconciliation jobs fail with error OPERATIONS_ERROR.
    Connection to LDAP looks OK, new users created in OIM are synchronized to LDAP, just Reconciliation jobs fail:
    <May 1, 2012 10:00:50 AM CEST> <Error> <oracle.iam.platform.entitymgr.provider.ldap> <IAM-0042016> <An error occurred while getting the change log from LDAP - {0}
    javax.naming.NamingException: Error: OPERATIONS_ERROR
    Virtualization Session closed [Root exception is oracle.ods.virtualization.service.VirtualizationException: Virtualization Session closed]
    at oracle.ods.virtualization.jndi.OVDUtil.mapErrorCode(OVDUtil.java:200)
    at oracle.ods.virtualization.jndi.OVDContext.search(OVDContext.java:439)
    at oracle.ods.virtualization.jndi.OVDContext.search(OVDContext.java:329)
    at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:248)
    at oracle.iam.platform.entitymgr.provider.ldap.LDAPUtil.search(LDAPUtil.java:1049)
    at oracle.iam.platform.entitymgr.provider.ldap.LDAPDataProvider.getChangelogResults(LDAPDataProvider.java:1531)
    at oracle.iam.platform.entitymgr.provider.ldap.LDAPDataProvider.deltaDetect(LDAPDataProvider.java:1488)
    at oracle.iam.ldapsync.scheduletasks.user.LDAPUserChangesReconTask.execute(LDAPUserChangesReconTask.java:152)
    at oracle.iam.scheduler.vo.TaskSupport.executeJob(TaskSupport.java:145)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at oracle.iam.scheduler.impl.quartz.QuartzJob.execute(QuartzJob.java:196)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
    at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
    Caused By: oracle.ods.virtualization.service.VirtualizationException: Virtualization Session closed
    at oracle.ods.virtualization.service.DefaultVirtualizationSession.checkActiveAndIncrementOp(DefaultVirtualizationSession.java:425)
    at oracle.ods.virtualization.service.DefaultVirtualizationSession.search(DefaultVirtualizationSession.java:183)
    at oracle.ods.virtualization.jndi.OVDContext.search(OVDContext.java:429)
    at oracle.ods.virtualization.jndi.OVDContext.search(OVDContext.java:329)
    at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:248)
    at oracle.iam.platform.entitymgr.provider.ldap.LDAPDataProvider.deltaDetect(LDAPDataProvider.java:1488)
    at oracle.iam.ldapsync.scheduletasks.user.LDAPUserChangesReconTask.execute(LDAPUserChangesReconTask.java:152)
    at oracle.iam.scheduler.vo.TaskSupport.executeJob(TaskSupport.java:146)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at oracle.iam.scheduler.impl.quartz.QuartzJob.execute(QuartzJob.java:198)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:203)
    at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529)
    ===
    Reconciliation worked before integrating OIM with OAM.
    Any ideas what could be wrong - or how to investigate this issue?
    Thanks
    Daniel

    OVD changelog adapter was OK, but OVD URL was missing in the IT resource.
    Reconciliation works now.
    Thanks for pointing me to correct direction.
    Daniel

  • Job failed with error tempdb is not available

    HI All,
    Backup job failed with error 'Unable to determine if the owner () of job backup_all_user_db_full has server access (reason: The log for database 'tempdb' is not available. [SQLSTATE HY000] (Error 9001)).'
    I checked in errorlog
    LogWriter: Operating system error 1784(The supplied user buffer is not valid for the requested operation.) encountered.                                        
                        Write error during log flush. Shutting down server
    2014-09-09 07:46:25.90 spid52    Error: 9001, Severity: 21, State: 1
    2014-09-09 07:46:25.90 spid52    The log for database 'tempdb' is not available..
    2014-09-09 07:46:25.92 spid51    Error: 9001, Severity: 21, State: 1
    Can anyone suggest to why it is happening

    From the error message, it looks like the drive on which the tempdb log file is residing is having issues. 
    Please involve your storage admin to look into the disk subsystem

  • SQL Server Agent job fails with error : The package execution returned DTSER_FAILURE (1).

    Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 10:00:01 AM Error: 2014-08-15 10:00:07.20
    Code: 0xC0047062 Source: Data Flow Task LEAN [6761]
    Description: Teradata.Client.Provider.TdException: [Teradata Database] [3006] Logons are disabled.
    at Teradata.Client.Provider.WpMessageManager.CheckForError()
    at Teradata.Client.Provider.WpMessageManager.ProcessResponse()
    at Teradata.Client.Provider.WpLogonManager.Action()
    at Teradata.Client.Provider.WpSession.ManagerAction(WpMessageManager manager, UtlStopwatchWrapper watch, Int32 connectionTimeout)
    at Teradata.Client.Provider.WpSession.Open(Int32 connectionTimeout, String password)
    at Teradata.Client.Provider.WpSession.Open(Int32 connectionTimeout)
    at Teradata.Client.Provider.Connection.Open(UtlConnectionString connectionString, UInt32 timeout)
    at Teradata.Client.Provider.ConnectionPool.CreateConnection(UInt32 timeout)
    at Teradata.Client.Provider.ConnectionPool.GetConnectionFromPool(Object owningObject)
    at Teradata.Client.Provider.ConnectionFactory.GetConnection(Object owningObject, UtlConnectionString connStr)
    at Teradata.Client.Provider.TdConnection.Open()
    at Microsoft.SqlServer.Dts.Runtime.ManagedHelper.GetManagedConnection(String assemblyQualifiedName, String connStr, Object transaction)
    at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager100.AcquireConnection(Object pTransaction)
    at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction)
    at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper100 wrapper, Object transaction)
    End Error Error: 2014-08-15 10:00:07.35 Code: 0xC0047017 Source: Data Flow Task SSIS.Pipeline
    Description: component "LEAN" (6761) failed validation and returned error code 0x80004005. End Error Error: 2014-08-15 10:00:07.48
    Code: 0xC004700C Source: Data Flow Task SSIS.Pipeline Description: One or more component failed validation.
    End Error Error: 2014-08-15 10:00:07.60 Code: 0xC0024107 Source: Data Flow Task
    Description: There were errors during task validation. End Error
    DTExec: The package execution returned DTSER_FAILURE (1). Started: 10:00:01 AM Finished: 10:00:07 AM
    Elapsed: 6.692 seconds. The package execution failed. The step failed.
    SQL Server agent job fails with above error, Please let me know process tohandle it.
    Thanks,
    Vishal.

    The error message suggests its the issue with Teradata source database to which SSIS tries to connect within the data flow task. Make sure Teradata database is available and LOGON is enabled.
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • Project Server 2010 - Update Scheduled Queue job failed with error message" Error no 131- AssignmentAlreadyExists"

    Hello,
    When I tried to update the schedule of the project , the job failed with the error message " AssignmentAlreadyExists". I further looked into the ULS logs but it wasn't that helpful.
    This is the message I found in ULS logs "type = UpdateScheduledProject failed at Message 5 and is blocking the correlation Errors: AssignmentAlreadyExists,Leaving Monitored Scope (FillTypedDataSet -- MSP_WEB_SP_QRY_ReadTimeSheetAssignmentsAndCustomFieldData).
    Execution Time=398.730006187937"
    Pplease help me to understand the root cause of this problem.
    I have verified all the assignments in the plan and I did not find any duplicates.
    Thanks in advance.
    Sesha

    This issue might need detailed troubleshooting, I would suggest you raise a support case with Microsoft.
    Cheers! Happy troubleshooting !!! Dinesh S. Rai - MSFT Enterprise Project Management Please click Mark As Answer; if a post solves your problem or Vote As Helpful if a post has been useful to you. This can be beneficial to other community members reading
    the thread.

  • Scheduled TMS_ # TMS_TP_IMPORT  background jobs fail with error code 0232

    Is anyone else having the problem we've just encountered since upgrading to ECC 6.0 and CRM 2007, where once setting up the automatic import ALL background jobs, to have all of the Transport Change Requests imported into the Q-Prod testing systems automatically, fail after several successful runs?
    After setting up the automatic import background job to run every 15 minutes, the first few run successfully (importing any transports as it should), then the transports stop being imported.
    The background jobs continue to run, but have the following in the job log overviews CRM 2007 - "Could not start transport control program tp". R\3 ECC 6.0 - "Transport control program tp ended with error code 0232".
    Only by deleting the background job and recreating it (or manually importing) from STMS, can the transports continue to be imported. Although I have noticed that there are multiple tp.exe processes started, which need to be deleted before the STMS and TMS Background jobs work again.
    The:
       DB is SQL Server 2005
       disp+work is at version 7000.150.14.48855
       R3Trans is at version 7000.149.14.47907
       tp is at version 7000.144.14.39594
    Any suggestions on how to cure this for good?

    Thanks All
    FYI
    SAP first suggested the following notes: 19466, 1150361, and to add a Startup profile parameter rfc/use_gwstart = 1. Which was only partially successful.
    I guess it had more to do with RFC processes hanging than it did with the tp, which was fixed in a later kernel patch level.
    I've upgraded the kernel to the latest (70000.181.0.0) and my problem was fixed.
    Ken

  • DB13 Job fail with error :Database instance is shut down

    Hi All,
    Recently we upgraded our Redhat Linux, Database from 9i to 10.2.0.4 and SAP Kernel 640 to patch 347.
    Now my system is working fine but in DB13 jobs I am getting error:
    Job started
    Step 001 started (program RSDBAJOB, variant &0000000000763, user ID SHMITTAL)
    Execute logical command BRCONNECT On host saturn
    Parameters: -u / -c -f stats -t ALL
    BR0801I BRCONNECT 6.40 (52)
    BR0805I Start of BRCONNECT processing: cegcuesi.sta 2011-06-16 06.26.52
    BR0484I BRCONNECT log file: /oracle/PP0/sapcheck/cegcuesi.sta
    BR0613E Database instance PP0 is shut down
    BR0806I End of BRCONNECT processing: cegcuesi.sta2011-06-16 06.26.52
    BR0280I BRCONNECT time stamp: 2011-06-16 06.26.52
    BR0804I BRCONNECT terminated with errors
    External program terminated with exit code 3
    BRCONNECT returned error status E
    Job finished
    it is looking to me that somewhere still Oracle path is mentioned as of 9i version.
    I checked environment variables, Default profile, initSID.sap but not find any issue, checked on google it says check tnsnames.ora, I checked that file but there is no such parameter for Oracle home.
    Please suggest to resolve the issue.
    Shivam Mittal

    Shivam Mittal wrote:
    BR0801I BRCONNECT 6.40 (52)
    Hi,
    allthough I am not quite sure, because 9i is sooo old and 10.2 is even near out of maintanance,
    Kernel 6.40 is linked against a version 9 client thus forcing sidadm to work with a 9i environment.
    brtools 6.40 working as orasid (environment 10g)
    and failing as sidadm (in the 6.40 plain kernel environment (oracle 9i))
    is perfectly normal as far as I remember.
    I think there was a section in the version 10 upg-guide whichg says to switch brtools to version 7.0, even if you use a 6.40 kernel exactly for this reason. This is, because version 7.0 brtools are hardlinked against the instantclient 10.
    So these work even as sidadm with an environment set to a version 9 client.
    I can not verify exactly, any more, cause all our 6.40 systems have recently gone to oracle version 11
    requireing the switch to the 6.40 EX2 kernel and brtools 7.20.
    Try brtools 7.00 on current patchlevel.
    Volker

  • Backup job failing with error ORA-12546: TNS:permission denied

    Hi All
    This is regarding one backup job running on windows server 2003 failing with below error.. when we are running this job manually that is running fine.. but not running from windows scheduler.
    its 9.2.0.1 and the 32 bit... windows 2003 64 bit
    Recovery Manager: Release 9.2.0.1.0 - Production
    Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-04005: error from target database:
    ORA-12546: TNS:permission denied
    Please help.
    Edited by: 811427 on Sep 6, 2011 12:36 AM

    I assume you installed Oracle as "Administrator" user. If so, make sure you are running the job from the same user. Optionally open "services.msc" and go to the "ORCL Service" or whatever it may and check "Log on" tab. It should be "logon as" value should be "Local system". If you are using a domain then give credentials accordingly. Make sure you are part of "DBA" group.
    The ORA-12546 TNS:permission denied points to "Insufficient permissions to trace/log files" - check the trace/log destination is writable and requisite permissions are given.

  • OEM12c jobs fail with "Error attempting to invoke console command"

    Hi gurus,
    I'm wondering if someone could help me on this issue.
    When I try to execute a job it remains in "Running" state for a long time periord and looking at the jobs details I can see something like this:
    Execution: DB11G.WORLD
         DB11G.WORLD     Running     Aug 29, 2012 10:17:31 AM GMT+02:00          57.9 minutes
    Step: DeployDriver     DB11G.WORLD     Scheduled
    Doing drilldown in "Scheduled" hiperlynk the message displayed is that:
    Error attempting to invoke console command, retrying
    And this is the Tip offered by oem:
         TIP:      Management Service from which the job step was dispatched.
    Everything seems to be working even the Management Service, but any job launched fail in the same way.
    Environment:
    Oem12c 12.1.0.1.0 with last patch
    Oracle Linux 5.7
    DB Oracle 11gr2
    Any suggestion on this issue will be welcome.
    Thanks,
    Carlos.

    Thanks Eric for your feedback.
    It seems that the problem was related with target "Oracle Authorization Policy Manager" because this target was down and after restart OMS and check that this target was up again all pending jobs worked and finished.
    However the job_queue_processes value was a good point to take into account so I increase this parameter just in case.
    Thanks,
    Carlos.
    QUERY STATUS = SOLVED

  • Backup job fails with error

    The error message is: RemoteOperationException: Failed to establish input-streaming thread
    In researching this, there was an article that talked about increasing the ThreadPool to MEDIUM. But this didn't help.
    If I retry the backup after it fails, it runs without any problem.
    This is GC 10.2.0.3 on Sun Solaris. Does anyone have a workaround for this?
    Thanks.

    Try this script...
    File Naming Format DBname_YYYYDDMM.BAK
    DECLARE @name VARCHAR(50) -- database name
    DECLARE @path VARCHAR(256) -- path for backup files
    DECLARE @fileName VARCHAR(256) -- filename for backup
    DECLARE @fileDate VARCHAR(20) -- used for file name
    -- specify database backup directory
    SET @path = 'C:\Backup\'
    -- specify filename format
    SELECT @fileDate = CONVERT(VARCHAR(20),GETDATE(),112)
    DECLARE db_cursor CURSOR FOR
    SELECT name
    FROM master.dbo.sysdatabases
    WHERE name NOT IN ('master','model','msdb','tempdb') -- exclude these databases
    OPEN db_cursor
    FETCH NEXT FROM db_cursor INTO @name
    WHILE @@FETCH_STATUS = 0
    BEGIN
    SET @fileName = @path + @name + '_' + @fileDate + '.BAK'
    BACKUP DATABASE @name TO DISK = @fileName
    FETCH NEXT FROM db_cursor INTO @name
    END
    CLOSE db_cursor
    DEALLOCATE db_cursor
    File Naming Format DBname_YYYYDDMM_HHMMSS.BAK
    If you want to also include the time in the filename you can replace this line in the above script:
    -- specify filename format
    SELECT @fileDate = CONVERT(VARCHAR(20),GETDATE(),112)
    with this line:
    -- specify filename format
    SELECT @fileDate = CONVERT(VARCHAR(20),GETDATE(),112) + REPLACE(CONVERT(VARCHAR(20),GETDATE(),108),':','')
    Raju Rasagounder Sr MSSQL DBA

  • SQL Backup fails with error 87 parameter incorrect

    I have a SQL Server 2008 R2 SP2 Standard instance working great, except upon attempts to use SQL backup to a UNC path hosted on Server 2012 R2, backup jobs fail with error 87 (the parameter is incorrect). When backing up to Server 2008 R2 and Server 2012
    shares, everything seems to work normally.
    Any experience with something like this? I've verified perms to the path and reachability in general, and it's clearly not an access denied error (which I've seen before).

    Thanks Alberto - I've verified that user (it's a domain user) has full access perms on that path, and tested outside of SSMS.
    Detailed error:
     System 
      - Provider 
       [ Name]  MSSQLSERVER 
      - EventID 18210 
       [ Qualifiers]  49152 
       Level 2 
       Task 6 
       Keywords 0x80000000000000 
      - TimeCreated 
       [ SystemTime]  2014-05-13T15:57:52.000000000Z 
       EventRecordID 2083317 
       Channel Application 
       Computer GriffinSQL.[local domain here]
      - Security 
       [ UserID]  [guid here]
    - EventData 
       BackupIoRequest::ReportIoError 
       write 
       \\storage\backups\sql\testggg.bak 
       87(The parameter is incorrect.) 
       22470000100000000B0000004700520049004600460049004E00530051004C00000000000000 
    Binary data:
    In Words
    0000: 00004722 00000010 0000000B 00520047 
    0008: 00460049 00490046 0053004E 004C0051 
    0010: 00000000 0000   
    In Bytes
    0000: 22 47 00 00 10 00 00 00   "G......
    0008: 0B 00 00 00 47 00 52 00   ....G.R.
    0010: 49 00 46 00 46 00 49 00   I.F.F.I.
    0018: 4E 00 53 00 51 00 4C 00   N.S.Q.L.
    0020: 00 00 00 00 00 00         ......

  • ORA-27369: job of type EXECUTABLE failed with exit code: Unknown error

    Hello DBAs,
    I am trying to schedule a shell script through dbms_scheduler.CREATE_JOB
    My database version is 10.2.0.3.0.
    I can successfully schedule the job, but while running, it throwing ORA-27369 with out exit code.
    Given below are the actions performed -
    -- Created shel scripts-
    $ cat shell01.sh
    ./test.sh >> test.log
    $
    $ cat test.sh
    sqlplus -s "/ as sysdba" <<EOF
    SELECT SUBSTR(host_name,0,10) host_name, instance_name, status,TO_CHAR(startup_time,'dd-mm-yy hh24:mi:ss') startup_time
    FROM v\$instance;
    disconnect;
    exit;
    EOF
    -- Granting privileges - (eventhough I have tried from 'SYS' schema)
    GRANT create Job, create external job, execute any class, execute any program , manage scheduler to sys;
    -- Drop job with name RUN_SHELL01
    BEGIN
    dbms_scheduler.drop_job('RUN_SHELL01');
    END;
    -- Schedule job with name RUN_SHELL01
    BEGIN
    dbms_scheduler.CREATE_JOB
         (job_name           => 'RUN_SHELL01',
         job_type           => 'EXECUTABLE',
         job_action           => '/home/ora1023/shell01.sh',
    start_date           => '18-AUG-09 05:37:00 AM',
         end_date          => NULL,
         repeat_interval      => 'FREQ=MINUTELY',
         enabled           => false,
         comments           => 'Run shell-script');
    END;
    --Enable job
    BEGIN
    dbms_scheduler.enable('RUN_SHELL01');
    END;
    -- Checking status
    SELECT owner, job_name, enabled FROM dba_scheduler_jobs;
    select JOB_NAME,STATUS,ERROR# from dba_scheduler_job_run_details where job_name='RUN_SHELL01';
    -- Executing the job
    SQL> exec dbms_scheduler.run_job('RUN_SHELL01');
    BEGIN dbms_scheduler.run_job('RUN_SHELL01'); END;
    ERROR at line 1:
    ORA-27369: job of type EXECUTABLE failed with exit code: Unknown error
    ORA-06512: at "SYS.DBMS_ISCHED", line 150
    ORA-06512: at "SYS.DBMS_SCHEDULER", line 441
    ORA-06512: at line 1
    Anybody please suggest a solutions for this -

    My shell script will work as below -
    user01@test01:/home/user01 : cat shell01.sh
    ./test.sh >> test.log
    user01@test01:/home/user01 :
    user01@test01:/home/user01 :
    user01@test01:/home/user01 : cat test.sh
    sqlplus -s "/ as sysdba" <<EOF
    SELECT SUBSTR(host_name,0,10) host_name, instance_name, status,TO_CHAR(startup_time,'dd-mm-yy hh24:mi:ss') startup_time
    FROM v\$instance;
    disconnect;
    exit;
    EOF
    user01@test01:/home/user01 : ./shell01.sh
    user01@test01:/home/user01 : ls -ltr
    -rw-r--r-- 1 ora1023 dba 155 Aug 26 05:28 test.log
    user01@test01:/home/user01 : cat test.log
    HOST_NAME INSTANCE_NAME STATUS STARTUP_TIME
    test01 oft1 OPEN 18-08-09 08:22:45
    user01@test01:/home/user01 :
    ** I think this shell script is working fine! ..its only for testing..
    and while we are querying dba_scheduler_job_run_details for additional info-
    SQL> select s.STATUS ,s.ADDITIONAL_INFO from dba_scheduler_job_run_details s where s.job_name='RUN_SHELL01';
    STATUS
    ADDITIONAL_INFO
    STANDARD_ERROR="execve: Exec format error"
    FAILED
    ORA-27369: job of type EXECUTABLE failed with exit code: Unknown error
    STANDARD_ERROR="execve: Exec format error"
    I think Metalink Doc ID: 555160.1 (Schedular Job of Type 'EXECUTABLE' Fails with ORA-27369 "exit code: 255" STANDARD_ERROR="execve: Exec format error"). Will help me to solve this issue Since i am using ksh -
    # echo $SHELL
    /bin/ksh
    Edited by: Rajesh Menon on Aug 25, 2009 9:21 PM

  • ORA-27369: job of type EXECUTABLE failed with exit code: Unknown error STAN

    ORA-27369: job of type EXECUTABLE failed with exit code: Unknown error STANDARD_ERROR="execve: Exec format error"
    #!/usr/bin/ksh
    /bin/find /u08/oradba/S036/archlog -name "*.arc" -exec rm -f {} \;
    Simple shell script gives above error when scheduled through dbms_scheduler. I did check metalink notes everything seems to be in order.
    Thanks,
    Siva

    Hi,
    Make sure the script is set to be executable (chmod a+rx script.sh) and that /usr/bin/ksh exists and is executable.
    If it still doesn't work post the new error message and the output of "ls -l script.sh" and also your exact Oracle version. Also try running the shell script directly at the command line (e.g. ./script.sh).
    Hope this helps,
    Ravi.

  • Background job failing with license check error

    Hi Experts
    In our ERP 6.0 system ,all the background jobs are failing with license check error.
    Have checked the license in SLICENSE and the license is fine.
    There is no warning while users are loggign in ,but when any background job is runing its failing with error
    Job started
    Logon not possible (error in license check)
    Job cancelled after system exception ERROR_MESSAGE
    Also performed the license test which is failing
    F:\usr\sap\XX1\SYS\exe\uc\NTAMD64>saplicense -test pf=F:\usr\sap\XX1\SYS\profile
    \XX1_DVEBMGS00_host_xx
    Protocol saplicense test:
    Read sapsytem name
           ok, sapsytem name = XX1
    Read message server host
           ok, host = hostname
    Read message server service port
           ok, service port = sapmsXX1
    Connect to message server
           ok, connect done
    Read hardware key from message server
           ok, got hardware key
    Detach from message server
           ok, detached
    Check hardware key
           ok, hardware key = T0343073854
    Connect to database
           ok, connected
    Check license
           ok, check done
    Disconnect database
           ok, database disconnected
    test result: license test failed
    LICENSE system: XX1 hardware key: T0343073854 expiration_date:
            installation no:  key:
            userlimit: 0 productid: R3_BASIS
            system-nr:
    license expired ***
    Please suggest how to troubleshoot.
    Regards
    Ajay

    @Michael
    In SLICENSe the Hardware key field is not BLUE or BLACK and its showing the exact hardware key which i can see at OS level with saplicense -get command.
    @Jagadish
    Note is good refrence, i reiinstalled the Digitally signed license with saplikey command and it was successful.
    But still the license test is failing at OS Level..below is the command prompt output.
    ===================================================================
    F:\usr\sap\XX1\SYS\exe\uc\NTAMD64>saplikey -install C:\license_script_XX.txt pf
    =F:\usr\sap\XX\SYS\profile\XX_DVEBMGS00_mngsez148079
    SAP License Key Administration  -  Copyright (C) 2003 SAP AG
    2 SAP license key(s) successfully installed.
    F:\usr\sap\XX\SYS\exe\uc\NTAMD64>saplicense -test pf=F:\usr\sap\XX1\SYS\profile
    \MD1_DVEBMGS00_mngsez148079
    Protocol saplicense test:
    Read sapsytem name
           ok, sapsytem name = XX1
    Read message server host
           ok, host = host
    Read message server service port
           ok, service port = sapmsXX1
    Connect to message server
           ok, connect done
    Read hardware key from message server
           ok, got hardware key
    Detach from message server
           ok, detached
    Check hardware key
           ok, hardware key = T0343073854
    Connect to database
           ok, connected
    Check license
           ok, check done
    Disconnect database
           ok, database disconnected
    test result: license test failed
    LICENSE system: XX1 hardware key: T0343073854 expiration_date:
            installation no:  key:
            userlimit: 0 productid: R3_BASIS
            system-nr:
    license expired ***
    ============================================================
    @Juan
    The hardware key was changed and we requested a new license with new hardware key,system was runing fine for couple of weeks with all background jiobs for SPAM./SAINT Ok .We performed EHP4 on this system.
    But now this issue is here,so i guess we should troubleshoot.
    Please let me know any other pointers.
    Regards
    Ajay
    PS In SLICENSE new installed license is fine and all users can login.

  • SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has be

    Hello, I have a sql 2005 server, and I am a developer, with the database on my own machine.  It alwayws works for me but after some minutes the other developer cant work in the application
    He got this error
    Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.1.140]
    and When I see the log event after that error, it comes with another error.
    SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.1.140]
    He has IIS5 and me too.
    I created a user on the domain called ASPSYS with password, then in the IIS on anonymous authentication I put that user with that password, and it works, on both machines.
    and in the connection string I have.
    <add key="sqlconn" value="Data Source=ESTACION15;Initial Catalog=GescomDefinitiva;Integrated Security=SSPI; Trusted_Connection=true"/>
    I go to the profiler, and I see that when he browses a page, the database is accesed with user ASPSYS, but when I browse a page, the database is accesed with user SE\levalencia.
    Thats strange.
    The only way that the other developer can work again on the project is to restart the whole machine. He has windows xp profession, I have windows 2000.
    If you want me to send logs please tellme

    Well here's my problem, maybe you can help. Intermittenly I get a login failed when connecting to a db engine through Server Management Studio using Windows authentication. When this happens the following entries are generated on the server's application event log:
    Event Type:        Error
    Event Source:    MSSQLSERVER
    Event Category:                (4)
    Event ID:              17806
    Date:                     1/14/2009
    Time:                     10:41:31 AM
    User:                     N/A
    Computer:          <server name>
    Description:
    SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: <ip address>]
    Event Type:        Failure Audit
    Event Source:    MSSQLSERVER
    Event Category:                (4)
    Event ID:              18452
    Date:                     1/14/2009
    Time:                     10:41:31 AM
    User:                     N/A
    Computer:          <server name>
    Description:
    Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: <ip address>]
    I've already ensured that the server is set to mixed authentication mode. Oddly enough, the workaround that I've found is that if I remote desktop into the server, log in and then log back out, Management Studio is suddenly able to connect again. No idea why it works. 
    As I said before, it is intermitten. Some days it errors on login, other days it doesn't and there are no configuration changes between them. Also, both client and server are in the same domain and same site so there is no VPN or anything in between. I'm really quite stumped. Any help would be great, or if you can point me in the right direction of where to look. Thank you in advance!

Maybe you are looking for