oracle / oracle/oracle-database-operator

DBMS_SCHEDULER not working oraoperator oracle deployed pod

Open
#226 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
192
Forks
69
Avg merge
16h 13m
Merged PRs (30d)
1

Description

We have tried scheduling the backup using DBMS_SCHEDULER, which is not working. Is this supported in container environment?

SQL>
SQL> BEGIN
DBMS_SCHEDULER.create_job(
job_name => 'RMAN_FULL_BACKUP_JOB',
job_type => 'EXECUTABLE',
job_action => '/home/oracle/rman_full_backup.sh', -- path inside the pod
start_date => SYSTIMESTAMP,
repeat_interval => 'FREQ=HOURLY; INTERVAL=1', -- run every 1 hour
enabled => TRUE,
auto_drop => FALSE,
comments => 'RMAN Full Backup every 1 hour inside OraOperator pod'
);
END;
/ 2 3 4 5 6 7 8 9 10 11 12 13

PL/SQL procedure successfully completed.

SQL> BEGIN
DBMS_SCHEDULER.run_job('RMAN_FULL_BACKUP_JOB');
END;
/ 2 3 4
BEGIN
*
ERROR at line 1:
ORA-27370: job slave failed to launch a job of type EXECUTABLE
ORA-27300: OS system dependent operation:Waiting for extjob to send child
failed with status: 62
ORA-27301: OS failure message: Timer expired
ORA-27302: failure occurred at: sjsec 6d
ORA-06512: at "SYS.DBMS_ISCHED", line 242
ORA-06512: at "SYS.DBMS_SCHEDULER", line 566
ORA-06512: at line 2
SQL>

=======
SQL> BEGIN
DBMS_SCHEDULER.run_job('RMAN_FULL_BACKUP_JOB');
END;
/ 2 3 4
BEGIN
*
ERROR at line 1:
ORA-27369: job of type EXECUTABLE failed with exit code: 7 Invalid username or
password
ORA-06512: at "SYS.DBMS_ISCHED", line 242
ORA-06512: at "SYS.DBMS_SCHEDULER", line 566
ORA-06512: at line 2

SQL>

2026-03-30T13:49:17.107893+00:00
PSMFPDB(3):Errors in file /opt/oracle/diag/rdbms/psmf/PSMF/trace/PSMF_j000_336474.trc:
ORA-12012: error on auto execute of job "SYSTEM"."RMAN_FULL_BACKUP_JOB"
ORA-27369: job of type EXECUTABLE failed with exit code: 7 Invalid username or password

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file or test is named. Start by reviewing how the operator configures the database pod and by reproducing the DBMS_SCHEDULER EXECUTABLE job errors shown in the issue; determine whether executable scheduler jobs are supported in this container environment and document the supported behavior or required configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes, sql
Domain
databases, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.