Troubleshooting the "buffer busy wait" event with parameters
p1=212
p2=2
p3=13
i decided to dump the block #2 in database file # 212.
The simple command:
alter system dump datafile 212 block 2;
generated the error message in trace file:
ERROR: alter system dump datafile/tempfile: invalid input file # 212
Should i use TEMPfile keywork? And the 2nd run
alter system dump tempfile 212 block 2;
brought the same error message to the trace file :(((.
The working syntax: use the file name (not a number)
alter system dump tempfile '+DATA/STAGESTB/TEMPFILE/TMP03.1566.1191597171' block 2;
The syntax:
ALTER SYSTEM DUMP { DATAFILE | TEMPFILE } { file_num | 'file_name' } { BLOCK block_num | [ BLOCK MIN block_num ] BLOCK MAX block_num } ;
Oracle, Exadata, Crossplatform migration, RAC, Performance, Troubleshooting. The views expressed on this blog are my own and do not necessarily reflect the views of Oracle.
Showing posts with label DUMP. Show all posts
Showing posts with label DUMP. Show all posts
Wednesday, July 30, 2025
ERROR: alter system dump datafile/tempfile: invalid input file
Subscribe to:
Posts (Atom)
# ocrconfig -add +DATA PROT-30: The Oracle Cluster Registry location to be added is not usable. PROC-50: The Oracle Cluster Registry locatio...
-
ILOM Java problem: "No appropriate protocol (protocol is disabled or cipher suites are inappropriate)" Usually above 3 s...
-
As we know, the End of Support becomes after 5 years after the End of Manufacturing (End of Life in Oracle terminology). So here is the ...