Example of exporting as sys user :
expdp \'/
as sysdba @LMSP\' directory=DATA_PUMP_DIR dumpfile=test.dmp log=test.log
tables=LMS_OWNER.REFERENCE_PARCEL_LINEAGES
Oracle Passwords - Hmmm
I was asked a question regarding the Oracle password policy in 12c.
Oracle provides a set of minimum requirements for passwords.
Passwords can be at most 30 bytes long. There are a variety of ways that you can secure passwords, ranging from requiring passwords to be of a sensible length, to creating custom password complexity verification scripts, that enforce the password complexity policy requirements, that apply at your site.
See the additional guidelines described in Guidelines for Securing Passwords.
https://docs.oracle.com/database/121/DBSEG/authentication.htm#DBSEG33223
docs.oracle.com
Configuring Authentication
You can configure Oracle Database to authenticate (that is, verify the identity of) users or other entities that connect to the database. Authentication can be configured in a variety of ways, such as through the database itself, from the operating system, or across the network.
Tried to create a password with 30 characters which worked but with 31characters as expected :
SQL> create user test identified by "abcdefghijklmnopqrstuvwxyz12345";
create user test identified by "abcdefghijklmnopqrstuvwxyz12345"
*
ERROR at line 1:
ORA-00972: identifier is too
long
However, had an issue with a password that was created using PL/SQL and you CAN'T use a password starting with a numeric value when using PL/SQL - think Oracle need to sort this one out.
Found this link and yes you can double quote the password but not consistent.
https://community.oracle.com/thread/2418402
Oracle provides a set of minimum requirements for passwords.
Passwords can be at most 30 bytes long. There are a variety of ways that you can secure passwords, ranging from requiring passwords to be of a sensible length, to creating custom password complexity verification scripts, that enforce the password complexity policy requirements, that apply at your site.
See the additional guidelines described in Guidelines for Securing Passwords.
https://docs.oracle.com/database/121/DBSEG/authentication.htm#DBSEG33223
Configuring Authentication
You can configure Oracle Database to authenticate (that is, verify the identity of) users or other entities that connect to the database. Authentication can be configured in a variety of ways, such as through the database itself, from the operating system, or across the network.
Tried to create a password with 30 characters which worked but with 31characters as expected :
SQL> create user test identified by "abcdefghijklmnopqrstuvwxyz12345";
create user test identified by "abcdefghijklmnopqrstuvwxyz12345"
*
ERROR at line 1:
ORA-00972: identifier is too
long
However, had an issue with a password that was created using PL/SQL and you CAN'T use a password starting with a numeric value when using PL/SQL - think Oracle need to sort this one out.
Found this link and yes you can double quote the password but not consistent.
https://community.oracle.com/thread/2418402
DBA_JOBS
Just a note on DBA_JOBS so I don't forget - pain when looking for DBA_JOBS in google and all you get is actual oracle jobs.
To show broken jobs.
1* select JOB,BROKEN,FAILURES,SCHEMA_USER,LAST_DATE,LAST_SEC,INTERVAL from DBA_JOBS e.g. job 11 has failed 121 times.
SQL> /
JOB B FAILURES SCHEMA_USE LAST_DATE LAST_SEC INTERVAL
---------- - ---------- ---------- --------- -------------------------------- --------------------------------------------------
9 N 0 EDW 31-OCT-18 05:00:10 TRUNC(SYSDATE+1) + 5/24
10 N 0 DW_MAIN 31-OCT-18 23:42:39 SYSDATE + 5/1440
8 N 0 EDW 31-OCT-18 04:00:29 TRUNC(SYSDATE+1) + 4/24
11 N 121 DW_MAIN 31-OCT-18 09:34:24 SYSDATE + 5/1440
850 N DW_MAIN NEXT_RUN_TIME ('Update Card Statuses')
To show broken jobs.
1* select JOB,BROKEN,FAILURES,SCHEMA_USER,LAST_DATE,LAST_SEC,INTERVAL from DBA_JOBS e.g. job 11 has failed 121 times.
SQL> /
JOB B FAILURES SCHEMA_USE LAST_DATE LAST_SEC INTERVAL
---------- - ---------- ---------- --------- -------------------------------- --------------------------------------------------
9 N 0 EDW 31-OCT-18 05:00:10 TRUNC(SYSDATE+1) + 5/24
10 N 0 DW_MAIN 31-OCT-18 23:42:39 SYSDATE + 5/1440
8 N 0 EDW 31-OCT-18 04:00:29 TRUNC(SYSDATE+1) + 4/24
11 N 121 DW_MAIN 31-OCT-18 09:34:24 SYSDATE + 5/1440
850 N DW_MAIN NEXT_RUN_TIME ('Update Card Statuses')
Subscribe to:
Posts (Atom)