ORA-14400: inserted partition key does not map to any partition
NormanKrueger 110000QH3M Visits (13411)
This block describes the best practice to fix the partition error.
A typical warehouse proxy agent error in the RAS1 log :
The SY agent create the Partitions and save the Partitions as table_properties. There is no extra column in the tables.
PYYYYMMDD example: P20171104
a:) Check the WPA and SY agent configuration:
b:) Analyze the SY agent logs about cursors errors within Oracle.
Increased the number of cursors within Oracle
c:) Compare the jdbc driver of WPA and SY agent with the version of Oracle DB version:
d:) Reenter the user and passwords in the WPA and SY agent configuration.
e:) Extract the the following tables
f:) Find out which tables have the problem
g:) Set a additional SY agent trace in the UNIX/Linux - CAND
h:) Check the output of TEP Navigator -> Summarization and Pruning Agent --> Statistics --> Workspace -> Table Partition Statistics
i:) Select one unimportant detail table and drop it check whether a new partition will be written for this table
j:) Find out when the last partition has created and go back x days that was defined in the KHD_
APARs: IV63083 -> fp4 NO PARTITIONS IN RAW TABLES
IV62258 -> fp4 ALLOW THE USAGE OF A URL WITH REROUTING INFORMATION
IV62003 -> fp4 KSY CREATES INCORRECT PARTITIONS
IV52159 -> fp3 S&P AGENT FAILS TO ADD PARTITIONS TO TABLES USING AGTIM
IV51380 -> fp3 TABLE ROW OUTSIDE THE BOUNDS OF PARTITION RANGE.
Subscribe and follow us for all the latest information directly on your social feeds: