Kill, cancel, resume or restart datapump expdp and impdp jobs

The expdp and impdp utilities are command-line driven, but when starting them from the OS-prompt, one does not notice it. When you run impdp or expdp and use ‘ctrl-c’ and you want to kill, cancel, start or resume a job, you will end up in the datapump command prompt… now what?!

All command shown here can be used with expdp and impdp datapump. Continue reading

The expdp equivalent of ‘exp consistent=y’…

Update: Legacy Mode

In 11.2, Oracle introduced ‘legacy mode‘ options for expdp and impdp.

One now can use the old exp and imp parameters, including ‘CONSISTENT=Y’.

Legacy Mode Active due to the following parameters:
Legacy Mode Parameter: "consistent=TRUE" Location: Parameter File, Replaced with:
  "flashback_time=TO_TIMESTAMP('2013-05-07 07:18:29', 'YYYY-MM-DD HH24:MI:SS')"
Legacy Mode has set reuse_dumpfiles=true parameter.

For 11.1 and older, original post:

Last few weeks I have been exporting 10g databases for migrating them to 11g. I knew Export Data Pump was read consistent (I have been running into ORA-01555‘s), but I was surprised to see a ORA-02298 (parent keys not found) when importing:

Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
ORA-39083: Object type REF_CONSTRAINT failed to create with error:
ORA-02298: cannot validate (SCOTT.FK_SCALE_ID) - parent keys not found
Failing sql is:
ALTER TABLE "SCOTT"."SCALE_ID" ADD CONSTRAINT "FK_SCALE_ID" FOREIGN KEY ("SCALE_ID") REFERENCES "SCOTT"."SCALE" ("ID") ENABLE

I thought the expdp had made an consistent database dump, but didn’t! The FK’s present in SALARY were not present as PK’s in the SCALE table, so this could only mean the dump was not database consistent at all!

Solution: Using the flashback_time option

Continue reading

SQLPlus and Easy Connect without password on the command line

The Easy Connect Naming Method allows you to connect to a database service without having to configure Net Service Names.

The most found example on internet is the one with typing the password at the command prompt when starting sqlplus:

sqlplus username/password@[//]host[:port][/service_name]
$> sqlplus system/manager@db_machine:1521/db_servicename

However, this means that the password will be stored in you history of commands (linux). This is not really secure… but sqlplus does not accept it when no password is supplied when using easy connect.

Two solutions

If you want to login with easy connect without typing the password on the command line, you have two options: Continue reading

Use USE_DB_RECOVERY_FILE_DEST for self-managing deletion rules of the Archived Log files

When using the Fast Recovery Area for storing archive logs, one probably wants to use this location to make use of the self-managing deletion rules of files.

One of these rules is that files are obsolete under the retention policy are eligible for deletion. When for instance RMAN needs space for backup (without delete obsolete option), Oracle will do a similar ‘delete obsolete’ command to make space in the Fast Recovery Area.

For archived logs to be eligible, one MUST use the USE_DB_RECOVERY_FILE_DEST setting for log_archive_dest_x. If the actual location is used, Oracle does not include archived logs in the self-managing deletion rules of files!!! Continue reading

Public yum package ‘oracle-validated’ problems on 64bit OEL

I was preparing some fresh installed OEL5.5 machines for database software installation, but after running ‘yum install oracle-validated‘, the OUI did not pass the prerequisites on two packages. It seems it did not install unixODBC-devel x86_64 and libaio-devel x86_64.

Their Linux may be unbreakable, but their ‘oracle-validated’ package on the public yum server seemed to be broken. Continue reading

Theoretical problem when WebLogic’s NodeManager is using a start script

Many people will use the WebLogic’s NodeManager to use the start script for starting Managed Servers:

StartScriptEnabled=true

The NodeManager will start the Managed Server using the script and monitor the Managed Server when it fails.

One of the mistakes people can make is creating their own start script and start the Managed Server using ‘nohup &’ within this script: Metalink [ID 984122.1] and [ID 861098.1]. The script will finish and the server keeps running, but the NodeManager thinks the Managed Server has failed… Continue reading

Oracle Database version compatibility and support matrix

— Checked for relevance on Januari 21, 2017

The Oracle Database version compatibility matrix and version support status matrix are almost mandatory when installing or upgrading clients or servers.

For information about patches, go here: Oracle database patches for Linux and Windows (on Metalink).

For announcements of security fixes, go to Critical Patch Updates, Security Alerts and Third Party Bulletin.

Oracle Database client / server version compatibility matrix

Oracle calls this Client / Server Interoperability Support, Note ID 207303.1

Oracle Database version release support status matrix

Oracle calls this the Database Releases Support Status Summary, Note ID 161818.1

You will be redirected to Oracle Support and you must be registered to gain access to the pages. I did not include the matrices, because these change over time.

Oracle Information about Windows 32 / 64 bit database and client versions

Certification Information for Oracle Database on Microsoft Windows x64 (64-bit), Doc ID 1307195.1