	Product(s):	APM Implementation and Performance Management
	Version(s):	7
	Environment:	N/A
	Area:	N/A
	Subarea:	N/A

Problem Description

User tried to restore a blank APM database (copied from APM 7.12.5 installation folder) in Oracle 12c (Oracle 12.1.0.2). User the received a large amount of errors in the import log during the restoration:

ORA-39083: Object type TABLE:"FND"."APPROVALROUTE" failed to create with error:
ORA-60019: Creating initial extent of size 14 in tablespace of extent size 8
Failing sql is:
CREATE TABLE "FND"."APPROVALROUTE" ("APPROVESASSE" NUMBER(10,0), "APPROVESBIDD" NUMBER(10,0), "APPROVESCONT" NUMBER(10,0), "APPROVESPROJ" NUMBER(10,0), "APPROVESPO" NUMBER(10,0), "APPROVESREQ" NUMBER(10,0), "APPROVESWO" NUMBER(10,0), "APPROVESWR" NUMBER(10,0), "AUTOAPPRULE" NUMBER(10,0), "AUTOTHRESHLD_AMT" FLOAT(126), "HASAPPRVSALL" NUMB

User then tried to restore the empty APM database from 7.12.3 and it successfully imported.

Solution

The key statement in the import log is the ORA-60019, whereby Oracle is identifying that the problem is that it cannot change the extent (size) of the field in question, the preceding error (ORA-39083) is a more general error message.

ORA-60019 results from a change in the default Oracle db_securefile setting from "PERMITTED" in Oracle 11g to "PREFERRED" in Oracle 12c. For more detailed information, a google search of error code ORA-60019 will result in several returns explaining the change.

The user's Database Administrator (DBA) will need to update the setting with following;

alter system set db_securefile=PERMITTED scope=both

Note, several other alternatives may be taken at the DBA's discretion.

Restore of blank 7.12.5 APM Database in Oracle 12 c fails with error code ORA-60019

Problem Description

Solution

See Also