Job  LIS-BW-VB_APPLICATION_03_360  Failed

The job  LIS-BW-VB_APPLICATION_03_360   is being cancelled.
The job was  terminated with a short dump.
Please find below the error analysis
Short text of error message:
Structures have changed (sy-subrc=2)
Long text of error message:
Technical information about the message:
Message class....... "MCEX"
Number.............. 194
Variable 1.......... 2
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
This is regarding  inventory datasources . The delta records are not getting loaded into the BI due to the above short dump.
Termination occurred in the ABAP program "SAPLMCEX" - in "MCEX_UPDATE_03".
The main program was "RMCEXUP1 ".
Error in below code
IF I_TMSP_HASH = lf_tmsp_hash.
   gf_tmsp_hash_ok = true.
ENDIF.
case sy-subrc.
   when 0. " Compare OK - do nothing
   when 1. " Compare OK - do nothing
   when 2. " Compare not ok - abort
     message x194(mcex) with sy-subrc.   -
  Error in this line
   when others.
     message x193(mcex) with sy-subrc.
endcase.
endif.
This is production issue. Please respond as soon as possible
Regards,
Kiran

Hi Kiran,
Yes, most probably you have installed SP6 without clearing the delta and extraction Q and this has caused the issue.
I can understand that the extraction must have got piled up with huge entries by now. But understand that the the extraction Q is common to all datasources in the same application component. And there is no way you can selectively identify and process them. Hence to get the whole process going, you would have to compromise your delta and do a re-init. And that means you are losing records for all the datasource in that appln comp.
Now considering your question if you do a re-init for only 2 DS and leave the 3rd. Since I am not aware of the kind of changes the new package has brought and I will not be able confirm on that. But my take on this is - you anyways need to refill your setup for the other two Datasources. Try doing an init for the 2 DS's and see if you are able to run ur V3 job then. But if it fails then you'll have to do re-int for the 3rd as well. In either of the case you'll will have a full(repair/init) load running for each of the DS(since u've lost the deltas). Also Time and effort essentially will be the same in both the cases.
I suggest you test this in your development/Quality system to avoid complicating your production issue.
This link will help youi:
http://sapbibw2010.blogspot.com/2010/10/how-to-retain-deltas-when-you-change-lo.html
Regards,
Swati

Similar Messages

  • Job for httpd.service failed. See 'systemctl status httpd.service' and

    Hello,
    I am the problem. I change "/etc/httpd/conf/httpd.conf" to install php5 on apache.
    sudo systemctl start httpd
    Job for httpd.service failed. See 'systemctl status httpd.service' and 'journalctl -xn' for details.
    systemctl status httpd.service
    ● httpd.service - Apache Web Server
    Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled)
    Active: failed (Result: exit-code) since lun. 2014-08-25 12:19:31 CEST; 1min 18s ago
    Process: 2208 ExecStop=/usr/bin/apachectl graceful-stop (code=exited, status=1/FAILURE)
    Process: 2433 ExecStart=/usr/bin/apachectl start (code=exited, status=1/FAILURE)
    Main PID: 2060 (code=exited, status=0/SUCCESS)
    août 25 12:19:31 creaprog apachectl[2433]: httpd: Syntax error on line 66 o...y
    août 25 12:19:31 creaprog systemd[1]: httpd.service: control process exite...=1
    août 25 12:19:31 creaprog systemd[1]: Failed to start Apache Web Server.
    août 25 12:19:31 creaprog systemd[1]: Unit httpd.service entered failed state.
    Hint: Some lines were ellipsized, use -l to show in full.
    cat /etc/httpd/conf/httpd.conf
    # This is the main Apache HTTP server configuration file. It contains the
    # configuration directives that give the server its instructions.
    # See <URL:http://httpd.apache.org/docs/2.4/> for detailed information.
    # In particular, see
    # <URL:http://httpd.apache.org/docs/2.4/mod/directives.html>
    # for a discussion of each configuration directive.
    # Do NOT simply read the instructions in here without understanding
    # what they do. They're here only as hints or reminders. If you are unsure
    # consult the online docs. You have been warned.
    # Configuration and logfile names: If the filenames you specify for many
    # of the server's control files begin with "/" (or "drive:/" for Win32), the
    # server will use that explicit path. If the filenames do *not* begin
    # with "/", the value of ServerRoot is prepended -- so "logs/access_log"
    # with ServerRoot set to "/usr/local/apache2" will be interpreted by the
    # server as "/usr/local/apache2/logs/access_log", whereas "/logs/access_log"
    # will be interpreted as '/logs/access_log'.
    # ServerRoot: The top of the directory tree under which the server's
    # configuration, error, and log files are kept.
    # Do not add a slash at the end of the directory path. If you point
    # ServerRoot at a non-local disk, be sure to specify a local disk on the
    # Mutex directive, if file-based mutexes are used. If you wish to share the
    # same ServerRoot for multiple httpd daemons, you will need to change at
    # least PidFile.
    ServerRoot "/srv/http"
    # Mutex: Allows you to set the mutex mechanism and mutex file directory
    # for individual mutexes, or change the global defaults
    # Uncomment and change the directory if mutexes are file-based and the default
    # mutex file directory is not on a local disk or is not appropriate for some
    # other reason.
    # Mutex default:/run/httpd
    # Listen: Allows you to bind Apache to specific IP addresses and/or
    # ports, instead of the default. See also the <VirtualHost>
    # directive.
    # Change this to Listen on specific IP addresses as shown below to
    # prevent Apache from glomming onto all bound IP addresses.
    #Listen 12.34.56.78:80
    Listen 80
    # Dynamic Shared Object (DSO) Support
    # To be able to use the functionality of a module which was built as a DSO you
    # have to place corresponding `LoadModule' lines at this location so the
    # directives contained in it are actually available _before_ they are used.
    # Statically compiled modules (those listed by `httpd -l') do not need
    # to be loaded here.
    # Example:
    # LoadModule foo_module modules/mod_foo.so
    LoadModule authn_file_module modules/mod_authn_file.so
    #LoadModule authn_dbm_module modules/mod_authn_dbm.so
    #LoadModule authn_anon_module modules/mod_authn_anon.so
    #LoadModule authn_dbd_module modules/mod_authn_dbd.so
    #LoadModule authn_socache_module modules/mod_authn_socache.so
    LoadModule authn_core_module modules/mod_authn_core.so
    LoadModule authz_host_module modules/mod_authz_host.so
    LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
    LoadModule authz_user_module modules/mod_authz_user.so
    #LoadModule authz_dbm_module modules/mod_authz_dbm.so
    #LoadModule authz_owner_module modules/mod_authz_owner.so
    #LoadModule authz_dbd_module modules/mod_authz_dbd.so
    LoadModule authz_core_module modules/mod_authz_core.so
    #LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
    LoadModule access_compat_module modules/mod_access_compat.so
    LoadModule auth_basic_module modules/mod_auth_basic.so
    #LoadModule auth_form_module modules/mod_auth_form.so
    #LoadModule auth_digest_module modules/mod_auth_digest.so
    #LoadModule allowmethods_module modules/mod_allowmethods.so
    #LoadModule file_cache_module modules/mod_file_cache.so
    #LoadModule cache_module modules/mod_cache.so
    #LoadModule cache_disk_module modules/mod_cache_disk.so
    #LoadModule cache_socache_module modules/mod_cache_socache.so
    #LoadModule socache_shmcb_module modules/mod_socache_shmcb.so
    #LoadModule socache_dbm_module modules/mod_socache_dbm.so
    #LoadModule socache_memcache_module modules/mod_socache_memcache.so
    #LoadModule watchdog_module modules/mod_watchdog.so
    #LoadModule macro_module modules/mod_macro.so
    #LoadModule dbd_module modules/mod_dbd.so
    #LoadModule dumpio_module modules/mod_dumpio.so
    #LoadModule echo_module modules/mod_echo.so
    #LoadModule buffer_module modules/mod_buffer.so
    #LoadModule data_module modules/mod_data.so
    #LoadModule ratelimit_module modules/mod_ratelimit.so
    LoadModule reqtimeout_module modules/mod_reqtimeout.so
    #LoadModule ext_filter_module modules/mod_ext_filter.so
    #LoadModule request_module modules/mod_request.so
    LoadModule include_module modules/mod_include.so
    LoadModule filter_module modules/mod_filter.so
    #LoadModule reflector_module modules/mod_reflector.so
    #LoadModule substitute_module modules/mod_substitute.so
    #LoadModule sed_module modules/mod_sed.so
    #LoadModule charset_lite_module modules/mod_charset_lite.so
    #LoadModule deflate_module modules/mod_deflate.so
    #LoadModule xml2enc_module modules/mod_xml2enc.so
    #LoadModule proxy_html_module modules/mod_proxy_html.so
    LoadModule mime_module modules/mod_mime.so
    #LoadModule ldap_module modules/mod_ldap.so
    LoadModule log_config_module modules/mod_log_config.so
    #LoadModule log_debug_module modules/mod_log_debug.so
    #LoadModule log_forensic_module modules/mod_log_forensic.so
    #LoadModule logio_module modules/mod_logio.so
    #LoadModule lua_module modules/mod_lua.so
    LoadModule env_module modules/mod_env.so
    #LoadModule mime_magic_module modules/mod_mime_magic.so
    #LoadModule cern_meta_module modules/mod_cern_meta.so
    #LoadModule expires_module modules/mod_expires.so
    LoadModule headers_module modules/mod_headers.so
    #LoadModule ident_module modules/mod_ident.so
    #LoadModule usertrack_module modules/mod_usertrack.so
    #LoadModule unique_id_module modules/mod_unique_id.so
    LoadModule setenvif_module modules/mod_setenvif.so
    LoadModule version_module modules/mod_version.so
    #LoadModule remoteip_module modules/mod_remoteip.so
    LoadModule proxy_module modules/mod_proxy.so
    LoadModule proxy_connect_module modules/mod_proxy_connect.so
    LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
    LoadModule proxy_http_module modules/mod_proxy_http.so
    LoadModule proxy_fcgi_module modules/mod_proxy_fcgi.so
    LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
    #LoadModule proxy_fdpass_module modules/mod_proxy_fdpass.so
    LoadModule proxy_wstunnel_module modules/mod_proxy_wstunnel.so
    LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
    LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
    LoadModule proxy_express_module modules/mod_proxy_express.so
    #LoadModule session_module modules/mod_session.so
    #LoadModule session_cookie_module modules/mod_session_cookie.so
    #LoadModule session_crypto_module modules/mod_session_crypto.so
    #LoadModule session_dbd_module modules/mod_session_dbd.so
    LoadModule slotmem_shm_module modules/mod_slotmem_shm.so
    #LoadModule slotmem_plain_module modules/mod_slotmem_plain.so
    #LoadModule ssl_module modules/mod_ssl.so
    #LoadModule dialup_module modules/mod_dialup.so
    LoadModule lbmethod_byrequests_module modules/mod_lbmethod_byrequests.so
    LoadModule lbmethod_bytraffic_module modules/mod_lbmethod_bytraffic.so
    LoadModule lbmethod_bybusyness_module modules/mod_lbmethod_bybusyness.so
    LoadModule lbmethod_heartbeat_module modules/mod_lbmethod_heartbeat.so
    LoadModule mpm_event_module modules/mod_mpm_event.so
    LoadModule unixd_module modules/mod_unixd.so
    #LoadModule heartbeat_module modules/mod_heartbeat.so
    #LoadModule heartmonitor_module modules/mod_heartmonitor.so
    #LoadModule dav_module modules/mod_dav.so
    LoadModule status_module modules/mod_status.so
    LoadModule autoindex_module modules/mod_autoindex.so
    #LoadModule asis_module modules/mod_asis.so
    #LoadModule info_module modules/mod_info.so
    #LoadModule suexec_module modules/mod_suexec.so
    #LoadModule cgid_module modules/mod_cgid.so
    #LoadModule cgi_module modules/mod_cgi.so
    #LoadModule dav_fs_module modules/mod_dav_fs.so
    #LoadModule dav_lock_module modules/mod_dav_lock.so
    #LoadModule vhost_alias_module modules/mod_vhost_alias.so
    LoadModule negotiation_module modules/mod_negotiation.so
    LoadModule dir_module modules/mod_dir.so
    #LoadModule imagemap_module modules/mod_imagemap.so
    #LoadModule actions_module modules/mod_actions.so
    #LoadModule speling_module modules/mod_speling.so
    LoadModule userdir_module modules/mod_userdir.so
    LoadModule alias_module modules/mod_alias.so
    #LoadModule rewrite_module modules/mod_rewrite.so
    #Load php5 module
    LoadModule php5_module modules/libphp5.so
    <IfModule unixd_module>
    # If you wish httpd to run as a different user or group, you must run
    # httpd as root initially and it will switch.
    # User/Group: The name (or #number) of the user/group to run httpd as.
    # It is usually good practice to create a dedicated user and group for
    # running httpd, as with most system services.
    User http
    Group http
    </IfModule>
    # 'Main' server configuration
    # The directives in this section set up the values used by the 'main'
    # server, which responds to any requests that aren't handled by a
    # <VirtualHost> definition. These values also provide defaults for
    # any <VirtualHost> containers you may define later in the file.
    # All of these directives may appear inside <VirtualHost> containers,
    # in which case these default settings will be overridden for the
    # virtual host being defined.
    # ServerAdmin: Your address, where problems with the server should be
    # e-mailed. This address appears on some server-generated pages, such
    # as error documents. e.g. [email protected]
    ServerAdmin [email protected]
    # ServerName gives the name and port that the server uses to identify itself.
    # This can often be determined automatically, but we recommend you specify
    # it explicitly to prevent problems during startup.
    # If your host doesn't have a registered DNS name, enter its IP address here.
    #ServerName www.example.com:80
    # Deny access to the entirety of your server's filesystem. You must
    # explicitly permit access to web content directories in other
    # <Directory> blocks below.
    <Directory />
    AllowOverride none
    Require all denied
    </Directory>
    # Note that from this point forward you must specifically allow
    # particular features to be enabled - so if something's not working as
    # you might expect, make sure that you have specifically enabled it
    # below.
    # DocumentRoot: The directory out of which you will serve your
    # documents. By default, all requests are taken from this directory, but
    # symbolic links and aliases may be used to point to other locations.
    DocumentRoot "/srv/http"
    <Directory "/srv/http">
    # Possible values for the Options directive are "None", "All",
    # or any combination of:
    # Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
    # Note that "MultiViews" must be named *explicitly* --- "Options All"
    # doesn't give it to you.
    # The Options directive is both complicated and important. Please see
    # http://httpd.apache.org/docs/2.4/mod/core.html#options
    # for more information.
    Options Indexes FollowSymLinks
    # AllowOverride controls what directives may be placed in .htaccess files.
    # It can be "All", "None", or any combination of the keywords:
    # AllowOverride FileInfo AuthConfig Limit
    AllowOverride None
    # Controls who can get stuff from this server.
    Require all granted
    </Directory>
    # DirectoryIndex: sets the file that Apache will serve if a directory
    # is requested.
    <IfModule dir_module>
    DirectoryIndex index.html
    </IfModule>
    # The following lines prevent .htaccess and .htpasswd files from being
    # viewed by Web clients.
    <Files ".ht*">
    Require all denied
    </Files>
    # ErrorLog: The location of the error log file.
    # If you do not specify an ErrorLog directive within a <VirtualHost>
    # container, error messages relating to that virtual host will be
    # logged here. If you *do* define an error logfile for a <VirtualHost>
    # container, that host's errors will be logged there and not here.
    ErrorLog "/var/log/httpd/error_log"
    # LogLevel: Control the number of messages logged to the error_log.
    # Possible values include: debug, info, notice, warn, error, crit,
    # alert, emerg.
    LogLevel warn
    <IfModule log_config_module>
    # The following directives define some format nicknames for use with
    # a CustomLog directive (see below).
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
    LogFormat "%h %l %u %t \"%r\" %>s %b" common
    <IfModule logio_module>
    # You need to enable mod_logio.c to use %I and %O
    LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
    </IfModule>
    # The location and format of the access logfile (Common Logfile Format).
    # If you do not define any access logfiles within a <VirtualHost>
    # container, they will be logged here. Contrariwise, if you *do*
    # define per-<VirtualHost> access logfiles, transactions will be
    # logged therein and *not* in this file.
    CustomLog "/var/log/httpd/access_log" common
    # If you prefer a logfile with access, agent, and referer information
    # (Combined Logfile Format) you can use the following directive.
    #CustomLog "/var/log/httpd/access_log" combined
    </IfModule>
    <IfModule alias_module>
    # Redirect: Allows you to tell clients about documents that used to
    # exist in your server's namespace, but do not anymore. The client
    # will make a new request for the document at its new location.
    # Example:
    # Redirect permanent /foo http://www.example.com/bar
    # Alias: Maps web paths into filesystem paths and is used to
    # access content that does not live under the DocumentRoot.
    # Example:
    # Alias /webpath /full/filesystem/path
    # If you include a trailing / on /webpath then the server will
    # require it to be present in the URL. You will also likely
    # need to provide a <Directory> section to allow access to
    # the filesystem path.
    # ScriptAlias: This controls which directories contain server scripts.
    # ScriptAliases are essentially the same as Aliases, except that
    # documents in the target directory are treated as applications and
    # run by the server when requested rather than as documents sent to the
    # client. The same rules about trailing "/" apply to ScriptAlias
    # directives as to Alias.
    ScriptAlias /cgi-bin/ "/srv/http/cgi-bin/"
    </IfModule>
    <IfModule cgid_module>
    # ScriptSock: On threaded servers, designate the path to the UNIX
    # socket used to communicate with the CGI daemon of mod_cgid.
    #Scriptsock cgisock
    </IfModule>
    # "/srv/http/cgi-bin" should be changed to whatever your ScriptAliased
    # CGI directory exists, if you have that configured.
    <Directory "/srv/http/cgi-bin">
    AllowOverride None
    Options None
    Require all granted
    </Directory>
    <IfModule mime_module>
    # TypesConfig points to the file containing the list of mappings from
    # filename extension to MIME-type.
    TypesConfig conf/mime.types
    # AddType allows you to add to or override the MIME configuration
    # file specified in TypesConfig for specific file types.
    #AddType application/x-gzip .tgz
    # AddEncoding allows you to have certain browsers uncompress
    # information on the fly. Note: Not all browsers support this.
    #AddEncoding x-compress .Z
    #AddEncoding x-gzip .gz .tgz
    # If the AddEncoding directives above are commented-out, then you
    # probably should define those extensions to indicate media types:
    AddType application/x-compress .Z
    AddType application/x-gzip .gz .tgz
    # AddHandler allows you to map certain file extensions to "handlers":
    # actions unrelated to filetype. These can be either built into the server
    # or added with the Action directive (see below)
    # To use CGI scripts outside of ScriptAliased directories:
    # (You will also need to add "ExecCGI" to the "Options" directive.)
    #AddHandler cgi-script .cgi
    # For type maps (negotiated resources):
    #AddHandler type-map var
    # Filters allow you to process content before it is sent to the client.
    # To parse .shtml files for server-side includes (SSI):
    # (You will also need to add "Includes" to the "Options" directive.)
    #AddType text/html .shtml
    #AddOutputFilter INCLUDES .shtml
    </IfModule>
    # The mod_mime_magic module allows the server to use various hints from the
    # contents of the file itself to determine its type. The MIMEMagicFile
    # directive tells the module where the hint definitions are located.
    #MIMEMagicFile conf/magic
    # Customizable error responses come in three flavors:
    # 1) plain text 2) local redirects 3) external redirects
    # Some examples:
    #ErrorDocument 500 "The server made a boo boo."
    #ErrorDocument 404 /missing.html
    #ErrorDocument 404 "/cgi-bin/missing_handler.pl"
    #ErrorDocument 402 http://www.example.com/subscription_info.html
    # MaxRanges: Maximum number of Ranges in a request before
    # returning the entire resource, or one of the special
    # values 'default', 'none' or 'unlimited'.
    # Default setting is to accept 200 Ranges.
    #MaxRanges unlimited
    # EnableMMAP and EnableSendfile: On systems that support it,
    # memory-mapping or the sendfile syscall may be used to deliver
    # files. This usually improves server performance, but must
    # be turned off when serving from networked-mounted
    # filesystems or if support for these functions is otherwise
    # broken on your system.
    # Defaults: EnableMMAP On, EnableSendfile Off
    #EnableMMAP off
    #EnableSendfile on
    # Supplemental configuration
    # The configuration files in the conf/extra/ directory can be
    # included to add extra features or to modify the default configuration of
    # the server, or you may simply copy their contents here and change as
    # necessary.
    # Server-pool management (MPM specific)
    Include conf/extra/httpd-mpm.conf
    # Multi-language error messages
    Include conf/extra/httpd-multilang-errordoc.conf
    # Fancy directory listings
    Include conf/extra/httpd-autoindex.conf
    # Language settings
    Include conf/extra/httpd-languages.conf
    # User home directories
    Include conf/extra/httpd-userdir.conf
    # Real-time info on requests and configuration
    #Include conf/extra/httpd-info.conf
    # Virtual hosts
    #Include conf/extra/httpd-vhosts.conf
    # Local access to the Apache HTTP Server Manual
    #Include conf/extra/httpd-manual.conf
    # Distributed authoring and versioning (WebDAV)
    #Include conf/extra/httpd-dav.conf
    # Various default settings
    Include conf/extra/httpd-default.conf
    # PHP settings
    Include conf/extra/php5_module.conf
    # Configure mod_proxy_html to understand HTML4/XHTML1
    <IfModule proxy_html_module>
    Include conf/extra/proxy-html.conf
    </IfModule>
    # Secure (SSL/TLS) connections
    #Include conf/extra/httpd-ssl.conf
    # Note: The following must must be present to support
    # starting without SSL on platforms with no /dev/random equivalent
    # but a statically compiled-in mod_ssl.
    <IfModule ssl_module>
    SSLRandomSeed startup builtin
    SSLRandomSeed connect builtin
    </IfModule>
    # uncomment out the below to deal with user agents that deliberately
    # violate open standards by misusing DNT (DNT *must* be a specific
    # end-user choice)
    #<IfModule setenvif_module>
    #BrowserMatch "MSIE 10.0;" bad_DNT
    #</IfModule>
    #<IfModule headers_module>
    #RequestHeader unset DNT env=bad_DNT
    #</IfModule>
    Thanks, sorry my english is bad .
    Last edited by Creaprog (2014-08-25 10:25:17)

    I just noticed the exact same thing. It turns out that the httpd-ssl.conf file on my system is still the old v2.2 syntax, which means that the SSLMutex directive is still in there. This is an invalid directive after 2.2.
    This is where things get interesting. At first, I simply thought I had forgotten to merge httpd-ssl.conf.pacnew after apache had been upgraded to 2.4. However, when I check my pacman.log, it appears that httpd-ssl.conf was never upgraded when apache went to 2.4 - (2.2.26-1 -> 2.4.7-1). There was never a pacnew file generated to be merged.
    I took a look at the apache package via the abs and the "proper" httpd-ssl.conf is certainly in there, so why pacman never created a pacnew file is a mystery.
    Anyway, to fix this: pull the httpd-ssl.conf from the apache package, either from your cache, using the abs and building it, or (I think) pacman may re-install it if you move the file to a backup location (not sure about this). Then merge your original httpd-ssl-conf with the new one.

  • XI Job SAP_BC_XMB_DELETE_200 is getting failed

    HI Experts,
    in our XI system, the message archiving job SAP_BC_XMB_ARCHIVE200 finished successfully. but the deleting job SAP_BC_XMB_DELETE_200 is getting failed since 15 days. it run daily. below is the JOB Log.
    ====================================================
    Job started
    Step 001 started (program RSXMB_DELETE_MESSAGES, variant , user ID PISUPER
    Repeat terminated copy job first
    Job cancelled after system exception ERROR_MESSAGE
    ====================================================
    please advice.

    Hello!!
    You might find more info of this issue here:
    http://wiki.sdn.sap.com/wiki/display/XI/REPEATTERMINATEDCOPYJOBFIRST
    Cheers,
    Diego.

  • ORA-27369: job of type EXECUTABLE failed with exit code: Not owner

    Hi
    I created a backup RAC database job using DBMS_SCHEDULER under RMANTEST schema (a DBA account) and I got the error as subject.
    begin
    dbms_scheduler.create_job(
    job_name => 'scheduler_backup',
    job_type => 'EXECUTABLE',
    number_of_arguments => 2,
    job_action => '/opt/oracle/admin/bin/rman_fullbackup_RAC_TEST_test.sh',
    comments => 'backup via scheduler'
    dbms_scheduler.SET_JOB_ARGUMENT_VALUE('scheduler_backup', 1, 'TEST');
    dbms_scheduler.SET_JOB_ARGUMENT_VALUE('scheduler_backup', 2, 'TEST2');
    dbms_scheduler.enable('scheduler_backup');
    end;
    Thanks,
    Kevin

    Hi Ravi
    Thanks for your input.
    "ORA-27369: job of type EXECUTABLE failed with exit code: Not owner" is what I copied from ADDITIONAL_INFO of USER_SCHEDULER_JOB_RUB_DETAILS.
    One thing I don't understand of your words is that
    "On 10gR1 and 10gR2 you can redirect the stdout/stderr within your script and take a look at those log files."
    In my script, I have log files but I cannot see it. I guess the job fails directly without hitting the redirection line in the script. Do you mean I shall write something like this
    dbms_scheduler.create_job (
    job_action => '/opt/oracle/admin/bin/backup.sh > backup.log'
    Another one is
    "make sure that the user that external jobs run as must be able to run your script"
    But OS user and database user are two different accounts at different level.
    I am using 10.2.0.2 RAC. The Unix script runs successfully every night. I just want to take advantage of DBMS_SCHEDULER to avoid host dependency.
    Thanks,
    Kevin

  • ORA-27369: job of type EXECUTABLE failed with exit code: Key has expired

    Hi
    I defined the following Job on Linux Redhat 5.4 & Oracle DB 10.2.0.4:
    BEGIN
      dbms_scheduler.create_job(job_name        => 'expjob',
                                job_type        => 'executable',
                                job_action      => '/EXPORT/scott_cmd',
                                enabled         => TRUE,
                                auto_drop       => FALSE);
    END;
    drwxrwxrwx   2 oracle oinstall  4096 Jul 10 19:19 EXPORTwhere:
    /home/oracle>cat /EXPORT/scott_cmd
    #!/bin/sh
    exp parfile=./scott.par
    /home/oracle>cat /EXPORT/scott.par
    FILE=scott.dmp
    USERID=STRMADMIN/STRMADMIN
    OWNER=SCOTT
    LOG=scott.log
    /home/oracle>ls -l /EXPORT/scott_cmd
    -rwxr-xr-x 1 oracle oinstall 34 Jul 10 19:16 /EXPORT/scott_cmd
    /home/oracle>ls -l /u01/app/oracle/OraHome_1/rdbms/admin/externaljob.ora
    -rw-r--r-- 1 root oinstall 1575 Jul 10 18:42 /u01/app/oracle/OraHome_1/rdbms/admin/externaljob.ora
    (run_user = nobody
    run_group = nobody)
    /home/oracle>ls -l  /u01/app/oracle/OraHome_1/bin/extjob
    -rwsr-x--- 1 root oinstall 64842 Jul  8 14:21 /u01/app/oracle/OraHome_1/bin/extjob
    /home/oracle>ls -l  /u01/app/oracle/OraHome_1/bin/extjobo
    -rwxr-xr-x 1 oracle oinstall 64842 Jul  8 14:21 /u01/app/oracle/OraHome_1/bin/extjoboWhen I executed as user STRMADMIN ( has DBA & CREATE JOB Privileg) the Job, I got always the error:
    /EXPORT>sqlplus STRMADMIN/STRMADMIN
    SQL*Plus: Release 10.2.0.4.0 - Production on Sun Jul 10 19:40:24 2011
    Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> exec dbms_scheduler.run_job('expjob');
    BEGIN dbms_scheduler.run_job('expjob'); END;
    ERROR at line 1:
    ORA-27369: job of type EXECUTABLE failed with exit code: Key has expired
    ORA-06512: at "SYS.DBMS_ISCHED", line 150
    ORA-06512: at "SYS.DBMS_SCHEDULER", line 441
    ORA-06512: at line 1
    SQL>Please, help
    regards
    hqt200475
    Edited by: hqt200475 on Jul 10, 2011 10:04 AM
    Edited by: hqt200475 on Jul 10, 2011 10:05 AM

    Hi Ronald,
    I need the external Job in the 10.2.0.4-Environment because of the Online-Upgrade of a 10.2.0.4-Database to 11.2.0.2 with STREAMS. I want to start the old export from a PL/SQL-Procedure.
    Now returning to my problem:
    First: Change the run user to oracle:oinstall $ORACLE_HOME/rdbms/admin/externaljob.ora
    # This configuration file is used by dbms_scheduler when executing external
    # (operating system) jobs. It contains the user and group to run external
    # jobs as. It must only be writable by the owner and must be owned by root.
    # If extjob is not setuid then the only allowable run_user
    # is the user Oracle runs as and the only allowable run_group is the group
    # Oracle runs as.
    #run_user = nobody
    #run_group = nobody
    run_user = oracle
    run_group = oinstallsecond:
    /EXPORT>cat scott_cmd
    #!/bin/sh
    ORACLE_SID=STB;export ORACLE_SID
    ORACLE_HOME=/u01/app/oracle/OraHome_1;export ORACLE_HOME
    PATH=$ORACLE_HOME/bin:$ORACLE_HOME/opmn/bin:$PATH; export PATH
    LD_LIBRARY_PATH=$ORACLE_HOME/lib;export LD_LIBRARY_PATH
    /u01/app/oracle/OraHome_1/bin/exp parfile=/EXPORT/scott.parand:
    BEGIN
      dbms_scheduler.create_job(job_name        => 'expjob_r',
                                job_type        => 'executable',
                                job_action      => '/EXPORT/scott_cmd',
                                enabled         => TRUE,
                                auto_drop       => FALSE);
    END;
    /The manual execution of export as user oracle/oinstall was unproblematic, But I still got the error when running the following procedure :
    SQL> exec dbms_scheduler.run_job('expjob_r');
    BEGIN dbms_scheduler.run_job('expjob_r'); END;
    ERROR at line 1:
    ORA-27369: job of type EXECUTABLE failed with exit code: Operation not
    permitted
    ORA-06512: at "SYS.DBMS_ISCHED", line 150
    ORA-06512: at "SYS.DBMS_SCHEDULER", line 441
    ORA-06512: at line 1regards
    hqt200475

  • ORA-27369: job of type EXECUTABLE failed with exit code: Permission denied

    Guy's
    I am getting the same error
    my schema is having dba priveleges.
    CREATE OR REPLACE procedure abc_1 as
    begin
    dbms_scheduler.create_job(
    job_name=>'test_1',
    job_type=>'executable',
    job_action=>'/d02/oradata/shell_scripts/import_db_1.sh',
    enabled=>false,
    auto_drop=>true );
    end;
    CREATE OR REPLACE procedure abc_2 as
    --http://www.dba-oracle.com/t_dbms_scheduler_examples.htm
    --http://www.oradev.com/dbms_scheduler.jsp
    --http://forums.oracle.com/forums/thread.jspa?messageID=1352558&#1352558
    begin
    dbms_scheduler.run_job (job_name=>'test_1');
    end;
    SQL>
    SQL>
    SQL> exec abc_1
    PL/SQL procedure successfully completed.
    SQL> exec abc_2
    BEGIN abc_2; END;
    ERROR at line 1:
    ORA-27369: job of type EXECUTABLE failed with exit code: Permission denied
    ORA-06512: at "SYS.DBMS_ISCHED", line 150
    ORA-06512: at "SYS.DBMS_SCHEDULER", line 441
    ORA-06512: at "SYS.ABC_2", line 6
    ORA-06512: at line 1
    any one got the solution.pl pass it.
    TIA,

    Hi,
    If rdbms/admin/externaljob.ora exists (in 10.2.0.3 and up) then external jobs run as the user and group specified in this file which should be nobody by default.
    If it does not exist (in releases prior to 10.2.0.3) then external jobs run as the owner of bin/extjob which should be nobody by default.
    Because external jobs run as a lowly privileged user (nobody) by default, you need to make sure that this user can execute your script. Things to check for include
    1) Use full paths to all binaries or scripts in job_action or program_action as well as calls inside the script.
    2) Make sure all scripts start with #!/bin/sh or another command interpreter
    3) Make sure all scripts have the executable bit set and are executable by the user that external jobs run as
    4) Make sure that all required environment variables are set. External jobs by default do not have any environment variables set. For example, for an oracle import or export or sqlloader script you may need to set oracle_home, oracle_sid, ld_library_path and path environment variables in your script or source the required Oracle environment script.
    Hope this helps,
    Ravi.

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

    I am trying to run a shell script through dbms_scheduler. The Shell scripts calls the oracle procedure which insert a record to the Debug table.
    Code for generating the script
    declare
    begin
    dbms_scheduler.create_job(
              job_name=>'test_call_unix'
              ,job_type=>'executable'
              ,job_action=>'/carsd/Input/Current/BAM/calling_proc.sh'
              ,start_date => SYSDATE
              ,repeat_interval => 'FREQ=SECONDLY; INTERVAL=1'
              ,enabled=>TRUE
              ,auto_drop => TRUE
              ,comments=> 'Calling unxi sh'
    end;
    the shell script (calling_proc.sh)
    touch called.log
    sqlplus $ORA_USER/$ORA_PWD@$ORA_HOST << EOF1
    exec p1_sh;
    exit;
    EOF1
    I gave chmod 777 calling_proc.sh
    this the error which i got in ALL_SCHEDULER_JOB_RUN_DETAILS table
    ORA-27369: job of type EXECUTABLE failed with exit code: 274662
    STANDARD_ERROR="Oracle Scheduler error: Config file is not owned by root or is writable by group or other or extjob is not setuid and owned by root"
    Thanks in advance
    Jeeva.

    STANDARD_ERROR="Oracle Scheduler error: Config file is not owned by root or is writable by group or other or extjob is not setuid and owned by root"
    I gave chmod 777 calling_proc.sh
    comply with top line message!

  • ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function

    Hello,
    I am calling a windows bat file using dbms_scheduler and getting the following error. I have searched the forum and the internet and tried different switches and options. None of them solved my problem.
    Oracle Version: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    OracleJobScheduler is running as a service
    Error starting at line 1 in command:
    execute GET_RESULTS();
    Error report:
    ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
    ORA-06512: at "SYS.DBMS_ISCHED", line 185
    ORA-06512: at "SYS.DBMS_SCHEDULER", line 486
    ORA-06512: at "PS.GET_RESULTS", line 67
    ORA-06512: at line 1
    27369. 00000 - "job of type EXECUTABLE failed with exit code: %s"
    *Cause:    A problem was encountered while running a job of type EXECUTABLE.
    The cause of the actual problem is identified by the exit code.
    *Action:   Correct the cause of the exit code and reschedule the job.
    Here is the code for scheduler
          dbms_output.put_line(os_commandline || utlPath || fileSeparator || 'get.bat >nul')
          dbms_scheduler.create_job
          (   job_name          =>'PS_GET_RESULTS'
                , job_action        => os_commandline || utlPath || fileSeparator || 'get.bat >nul'
                , job_type          =>'executable'
                , enabled           =>false
                , auto_drop         =>false
                , start_date        =>systimestamp
          dbms_scheduler.run_job(job_name =>'PS_GET_RESULTS');The dbs_output prints a line which shows that the parameters os_commandline, utlPath and fileSeparator are set correctly.
         C:\windows\system32\cmd.exe /q /c E:\UTLDir\get.bat >nulThe windows file (get.bat) is:
         "C:\Program Files (x86)\WinSCP\Winscp.exe" /script=e:\utldir\get_resultsThis batch file passes a script file to the executable winscp.exe to get files from another server.
    The script file (get_results) is:
         option batch abort
         option confirm off
         open sftp://username:password@ipnumber:port -hostkey="ssh-rsa 1024 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
         cd /usr/dropbox/
         option transfer binary
         get *.results E:\UTLDir\Results\
         close
         exitI tested the batch file directly and works fine and "gets" the files from the server. But, invoking from Oracle dbms_scheduler fails with ORA-27369: job of type EXECUTABLE failed with exit code: Incorrect function.
    Appreciate your help and time in suggesting additional guidelines or pointers.
    Thanks,
    Rose

    Here is an update, if somebody else is having a similar problem.
    The ftp command "cd" to change the directories should be an absolute path. I was given a path "/usr/dropbox/", but on the server it actually corresponds to "/usr/local/apps/dropbox/". After updating the directory path, the scheduler worked fine in invoking the batch file for transferring the files.
    Thanks,
    Rose

  • ORA-27369:job of type EXECUTABLE failed with exit code + rman???

    Hi all,
    I was trying to execute job from 10G (10.2.01) Enterprise Manager Database Control, and got error below
    ORA-27369:job of type EXECUTABLE failed with exit code: Network is down STANDARD_ERROR="/home/oracle/scripts/backup/backupset_full:rman: command not found"
    Here is the file contents of backupset_full
    #!usr/bin/bash
    rman <<EOF
    connect catalog rman/rman@catrcv
    connect target sys/sys@test
    run{
    EXECUTE SCRIPT global_backup_full;
    quit
    EOF
    Here is the file content of global_backup_full script
    CREATE SCRIPT global_backup_full
    shutdown immediate;
    startup mount;
    allocate channel d1 device type DISK;
    backup as compressed backupset database;
    release channel d1;
    NOTE: I am running on bash shell environment.
    THANK YOU VERY MUCH in advance.
    Rich,

    You need to set ORACLE_HOME inside backupset_full script and possibly change rman to $ORACLE_HOME/bin/rman
    #!usr/bin/bash
    export ORACLE_HOME=<your_oracle_home _directory>
    $ORACLE_HOME/bin/rman <<EOF
    connect catalog rman/rman@catrcv
    connect target sys/sys@test
    run{
    EXECUTE SCRIPT global_backup_full;
    quit
    EOF
    Here is the file content of global_backup_full script
    CREATE SCRIPT global_backup_full
    shutdown immediate;
    startup mount;
    allocate channel d1 device type DISK;
    backup as compressed backupset database;
    release channel d1;
    }

  • ORA-27369: job of type EXECUTABLE failed with exit code:Operation notpermit

    I am getting this error
    ORA-27369: job of type EXECUTABLE failed with exit code: Operation not permitted.
    We have been using this for such a long time without any problems.this is the plsql scheduler :
    Please help
    BEGIN
    SYS.DBMS_SCHEDULER.CREATE_JOB
    job_name => 'PROD_LOAD_SL_FILES'
    ,start_date => TO_TIMESTAMP_TZ('2005/12/02 17:05:00.000000 -05:00','yyyy/mm/dd hh24:mi:ss.ff tzh:tzm')
    ,repeat_interval => NULL
    ,end_date => NULL
    ,job_class => 'DEFAULT_JOB_CLASS'
    ,job_type => 'EXECUTABLE'
    ,job_action => '/home/oracle/actual/payment_files/slc_prod/load_sl_files.sh'
    ,comments => 'Loads SL files, uploads logs to database and sends email to Disbursement and DBA teams'
    SYS.DBMS_SCHEDULER.SET_ATTRIBUTE
    ( name => 'PROD_LOAD_SL_FILES'
    ,attribute => 'RESTARTABLE'
    ,value => FALSE);
    SYS.DBMS_SCHEDULER.SET_ATTRIBUTE
    ( name => 'PROD_LOAD_SL_FILES'
    ,attribute => 'LOGGING_LEVEL'
    ,value => SYS.DBMS_SCHEDULER.LOGGING_RUNS);
    SYS.DBMS_SCHEDULER.SET_ATTRIBUTE_NULL
    ( name => 'PROD_LOAD_SL_FILES'
    ,attribute => 'MAX_FAILURES');
    SYS.DBMS_SCHEDULER.SET_ATTRIBUTE_NULL
    ( name => 'PROD_LOAD_SL_FILES'
    ,attribute => 'MAX_RUNS');
    BEGIN
    SYS.DBMS_SCHEDULER.SET_ATTRIBUTE
    ( name => 'PROD_LOAD_SL_FILES'
    ,attribute => 'STOP_ON_WINDOW_CLOSE'
    ,value => FALSE);
    EXCEPTION
    -- could fail if program is of type EXECUTABLE...
    WHEN OTHERS THEN
    NULL;
    END;
    SYS.DBMS_SCHEDULER.SET_ATTRIBUTE
    ( name => 'PROD_LOAD_SL_FILES'
    ,attribute => 'JOB_PRIORITY'
    ,value => 1);
    SYS.DBMS_SCHEDULER.SET_ATTRIBUTE_NULL
    ( name => 'PROD_LOAD_SL_FILES'
    ,attribute => 'SCHEDULE_LIMIT');
    SYS.DBMS_SCHEDULER.SET_ATTRIBUTE
    ( name => 'PROD_LOAD_SL_FILES'
    ,attribute => 'AUTO_DROP'
    ,value => FALSE);
    END;
    and this is part of the unix script get executed:
    [oracle@USAC-S009 slc_prod]$ cat load_sl_files.sh
    #!/bin/sh
    # FILEME: /home/oracle/actual/paytment_files/load_sl_files.sh
    # PURPOSE: Load SL files, email .log files
    # INSTRUCTIONS/COMMENTS/ASSUMPTIONS: Two SL files will be pulled down
    # MAINTENANCE LOG
    # REV# DATE AUTHOR QA-ed BY CHANGE DESCRIPTION KEY
    DATE=`/bin/date +%d%b%y_%H%M`
    HOME=/home/oracle
    export HOME
    ORACLE_HOME=/u01/app/oracle/product/10.2
    export ORACLE_HOME
    ORACLE_SID=em
    export ORACLE_SID
    PATH=/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/oracle/bin:/etc:/usr/local/bin:/u01/app/oracle/product/10.2/bin:/bin:/sbin:/usr/bin:/usr/sbin; export PATH
    SL_HOME=/home/oracle/actual/payment_files/slc_prod
    FILE_HOME=/opt/u02/home/usair
    # Call slc.sh to load files
    ssh usac09.usacad.loc > /home/oracle/actual/payment_files/slc_prod/slc.sh.log <<EOT
    /u01/app/oracle/slc.sh 2>&1
    sleep 120
    EOT
    # Move logs from usac09 to usac-s009
    #ssh usac09.usacad.loc >> /home/oracle/actual/payment_files/slc_prod/slc.sh.log <<EOT
    # /u01/app/oracle/move_logs.sh 2>&1
    # sleep 15
    #EOT
    .............

    Hi!
    I have shell scripts with number of mandatory parameters.
    How can I write it in sql procedure in order to create exact command line that shuold be executed in Linux?
    the procedure looks like :
    CREATE OR REPLACE procedure CRM.run_tts (p_tts_name in varchar2 )
    is
    v_tts_name varchar2(2000);
    v_job_name varchar2(2000);
    v_source varchar2(200);
    v_target varchar2(200);
    Begin
    v_tts_name := upper(p_tts_name);
    --if p_instance_type='P' then
    v_source := 'psdwh';
    v_target := 'pudwh';
    --end if;
    if v_tts_name is not null then
    v_job_name := 'run_tts_'||v_tts_name;
    v_source := '/-ssid/'||v_source;
    v_target := '/-tsid/'||v_target;
    v_tts_name := '/-tbsname/'||v_tts_name;
    DBMS_SCHEDULER.create_job (
    job_name => v_job_name,
    job_type => 'EXECUTABLE',
    job_action => '/tmp/trans_asm',
    start_date => SYSTIMESTAMP,
    number_of_arguments => 3,
    enabled => false,
    auto_drop => false);
    --dbms_scheduler.set_job_argument_value(job_name=>v_job_name,argument_position=>1,argument_value=>'/software/oracle/dba/scripts/bin/trans_asm.sh'||' '||c_rec.id||' '||'"'||c_rec.view_name||'"'||' '||v_setnum||' '||'"'||V_MACHINE_TYPE||'"'||' '||'"'||p_mode||'"');
    dbms_scheduler.set_job_argument_value(job_name=>v_job_name,argument_position=>1,argument_value=>v_source);
    dbms_scheduler.set_job_argument_value(job_name=>v_job_name,argument_position=>2,argument_value=>v_target);
    dbms_scheduler.set_job_argument_value(job_name=>v_job_name,argument_position=>3,argument_value=>v_tts_name);
    -- dbms_scheduler.set_job_argument_value(job_name=>v_job_name,argument_position=>1,argument_value=>'/software/oracle/dba/scripts/bin/trans_asm_ps.sh');
    --dbms_scheduler.set_job_argument_value(job_name=>v_job_name,argument_position=>1,argument_value=>'/tmp/test.sh');
    -- trans_asm -ssid tsdwh -tsid tudwh -tbsname DW_BILLING_TTS
    dbms_scheduler.enable(name=>v_job_name);
    end if;
    end;
    the command looks like :
    trans_asm -ssid psdwh -tsid pudwh -tbsname YOAV_TTS
    Thank you !
    Valerie

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

    am getting this error
    ORA-27369: job of type EXECUTABLE failed with exit code: Operation not permitted.
    We have been using this for such a long time without any problems.this is the plsql scheduler :
    Please help
    BEGIN
    SYS.DBMS_SCHEDULER.CREATE_JOB
    job_name => 'PROD_LOAD_SL_FILES'
    ,start_date => TO_TIMESTAMP_TZ('2005/12/02 17:05:00.000000 -05:00','yyyy/mm/dd hh24:mi:ss.ff tzh:tzm')
    ,repeat_interval => NULL
    ,end_date => NULL
    ,job_class => 'DEFAULT_JOB_CLASS'
    ,job_type => 'EXECUTABLE'
    ,job_action => '/home/oracle/actual/payment_files/slc_prod/load_sl_files.sh'
    ,comments => 'Loads SL files, uploads logs to database and sends email to Disbursement and DBA teams'
    SYS.DBMS_SCHEDULER.SET_ATTRIBUTE
    ( name => 'PROD_LOAD_SL_FILES'
    ,attribute => 'RESTARTABLE'
    ,value => FALSE);
    SYS.DBMS_SCHEDULER.SET_ATTRIBUTE
    ( name => 'PROD_LOAD_SL_FILES'
    ,attribute => 'LOGGING_LEVEL'
    ,value => SYS.DBMS_SCHEDULER.LOGGING_RUNS);
    SYS.DBMS_SCHEDULER.SET_ATTRIBUTE_NULL
    ( name => 'PROD_LOAD_SL_FILES'
    ,attribute => 'MAX_FAILURES');
    SYS.DBMS_SCHEDULER.SET_ATTRIBUTE_NULL
    ( name => 'PROD_LOAD_SL_FILES'
    ,attribute => 'MAX_RUNS');
    BEGIN
    SYS.DBMS_SCHEDULER.SET_ATTRIBUTE
    ( name => 'PROD_LOAD_SL_FILES'
    ,attribute => 'STOP_ON_WINDOW_CLOSE'
    ,value => FALSE);
    EXCEPTION
    -- could fail if program is of type EXECUTABLE...
    WHEN OTHERS THEN
    NULL;
    END;
    SYS.DBMS_SCHEDULER.SET_ATTRIBUTE
    ( name => 'PROD_LOAD_SL_FILES'
    ,attribute => 'JOB_PRIORITY'
    ,value => 1);
    SYS.DBMS_SCHEDULER.SET_ATTRIBUTE_NULL
    ( name => 'PROD_LOAD_SL_FILES'
    ,attribute => 'SCHEDULE_LIMIT');
    SYS.DBMS_SCHEDULER.SET_ATTRIBUTE
    ( name => 'PROD_LOAD_SL_FILES'
    ,attribute => 'AUTO_DROP'
    ,value => FALSE);
    END;
    and this is part of the unix script get executed:
    [oracle@USAC-S009 slc_prod]$ cat load_sl_files.sh
    #!/bin/sh
    # FILEME: /home/oracle/actual/paytment_files/load_sl_files.sh
    # PURPOSE: Load SL files, email .log files
    # INSTRUCTIONS/COMMENTS/ASSUMPTIONS: Two SL files will be pulled down
    # MAINTENANCE LOG
    # REV# DATE AUTHOR QA-ed BY CHANGE DESCRIPTION KEY
    DATE=`/bin/date +%d%b%y_%H%M`
    HOME=/home/oracle
    export HOME
    ORACLE_HOME=/u01/app/oracle/product/10.2
    export ORACLE_HOME
    ORACLE_SID=em
    export ORACLE_SID
    PATH=/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/oracle/bin:/etc:/usr/local/bin:/u01/app/oracle/product/10.2/bin:/bin:/sbin:/usr/bin:/usr/sbin; export PATH
    SL_HOME=/home/oracle/actual/payment_files/slc_prod
    FILE_HOME=/opt/u02/home/usair
    # Call slc.sh to load files
    ssh usac09.usacad.loc > /home/oracle/actual/payment_files/slc_prod/slc.sh.log <<EOT
    /u01/app/oracle/slc.sh 2>&1
    sleep 120
    EOT
    .............

    Hi,
    The user oracle who owns the scheduler already has permissions for the mailx and the same script is able to send notifications when run manully. Do I need to set additional permissions for scheduler ?
    Also the db version is 10.2.0.5.
    Thanks

  • 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: Is a name file

    I am getting this error when I try to execute a file using /bin/sh , I create the file, do a chmod on the file and remove the file but I am have trouble executing it even though I can execute it form the command line.
    ORA-27369: job of type EXECUTABLE failed with exit code: Is a name file
    STANDARD_ERROR="Segmentation Fault"
    139
    EXTERNAL_LOG_ID="job_77927_1275",
    ORA-27369: job of type EXECUTABLE failed with exit code: Transport endpoint is n
    ot connected
    STANDARD_ERROR="Abort - core dumped
    here is the code
    DBMS_SCHEDULER.CREATE_JOB(job_name=>'CHMOD_ON_CCL',
    job_type=>'EXECUTABLE',
    job_action=>'/bin/chmod',
    number_of_arguments=>2,
    enabled=>false,
    auto_drop=>true);
    DBMS_SCHEDULER.set_attribute('CHMOD_ON_CCL', 'credential_name', 'SCHED_USER');
    DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE(job_name=>'CHMOD_ON_CCL',
    argument_position=>1,
    argument_value=>'777');
    DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE(job_name=>'CHMOD_ON_CCL',
    argument_position=>2,
    argument_value=>l_directory || '/' || loc_file_name);
    DBMS_SCHEDULER.ENABLE('CHMOD_ON_CCL');
    --execute the CCL file, this will run the scheduler
    DBMS_SCHEDULER.CREATE_JOB(job_name=>'EXECUTE_CCL',
    job_type=>'EXECUTABLE',
    job_action=>'/bin/sh',
    number_of_arguments=>1,
    enabled=>false,
    auto_drop=>true);
    DBMS_SCHEDULER.set_attribute('EXECUTE_CCL', 'credential_name', 'SCHED_USER');
    DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE(job_name=>'EXECUTE_CCL',
    argument_position=>1,
    argument_value=>l_directory || '/' || loc_file_name);
    DBMS_SCHEDULER.ENABLE('EXECUTE_CCL');
    --remove CCL file after scheudler runs
    DBMS_SCHEDULER.CREATE_JOB(job_name=>'REMOVE_CCL',
    job_type=>'EXECUTABLE',
    job_action=>'/bin/rm',
    number_of_arguments=>1,
    enabled=>false,
    auto_drop=>true);
    DBMS_SCHEDULER.set_attribute('REMOVE_CCL', 'credential_name', 'SCHED_USER');
    DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE(job_name=>'REMOVE_CCL',
    argument_position=>1,
    argument_value=>l_directory || '/' || loc_file_name);
    DBMS_SCHEDULER.ENABLE('REMOVE_CCL');
    "

    No problem at all, you can do the same by getting the output from env and unset the variables that are defined there manually. Start with
    unset PATH
    unset ORACLE_HOME
    unset LD_LIBRATY_PATH
    ad start your script again from this environment. The scheduler launches the jobs in an environment where hardly any variable is defined.
    R.

  • ORA-27369: job of type EXECUTABLE failed with exit code: No such file or directory

    Hi,
    I am using the scheduler to take backup of the dev database and it was working fine. Then I added notification to the scripts and then the scheduler started failing with the following code .
    BEGIN dbms_scheduler.run_job('BACKUP_DEV'); END;
    ERROR at line 1:
    ORA-27369: job of type EXECUTABLE failed with exit code: No such file or
    directory
    ORA-06512: at "SYS.DBMS_ISCHED", line 150
    ORA-06512: at "SYS.DBMS_SCHEDULER", line 441
    ORA-06512: at line 1
    Here' the original which has no issues
    #!/bin/bash -x
    echo $@
    if [ -z "$ORACLE_HOME" ]; then
    source /path/oracle/.bash_profile
    fi
    RMAN="${ORACLE_HOME}/bin/rman";
    ${RMAN} $@
    exit $?
    And here's the one which gives me the errors. Also if I run this script from command line it works perfectly fine
    #!/bin/bash -x
    echo $@
    if [ -z "$ORACLE_HOME" ]; then
    source /path/oracle/.bash_profile
    fi
    RMAN="${ORACLE_HOME}/bin/rman";
    exec >> temp_log
    ${RMAN} $@
    /usr/bin/mailx -s "Backup status of $ORACLE_SID " [email protected] < temp_log
    /usr/bin/rm temp_log
    exit $?
    Pls let me know what could be the reason that the script fails with the scheduler.

    Hi,
    The user oracle who owns the scheduler already has permissions for the mailx and the same script is able to send notifications when run manully. Do I need to set additional permissions for scheduler ?
    Also the db version is 10.2.0.5.
    Thanks

  • 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.

Maybe you are looking for