How to use pfile in recover table command
(Doc ID 2430319.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.1 to 12.2.0.1 [Release 12.1 to 12.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Goal
NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the Oracle sample schema(s), Public Documentation delivered with an
Oracle database product or other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.
Oracle database product or other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.
For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:
Database Name: PROD
Table name: scott.test_tab
***************
This is very handy, when target database is having very large SGA (like 120 GB or more) ,
and when we need to recover a single table, but server does not have that much memory, or when their is limitation of supported hardware)
/*
initialization parameters used for automatic instance:
db_name=PROD
db_unique_name=ahDi_pitr_PROD
compatible=12.2.0
db_block_size=8192
db_files=200
diagnostic_dest=/u01/app/oracle/PROD/diag
_system_trig_enabled=FALSE
sga_target=40960M <<<<<<<<<<<<<<<<<<< HERE is the problem ( 40 GB )
processes=200
db_create_file_dest=/ACFSDUMP/PROD
log_archive_dest_1='location=/ACFSDUMP/PROD'
#No auxiliary parameter file used
*/
initialization parameters used for automatic instance:
db_name=PROD
db_unique_name=ahDi_pitr_PROD
compatible=12.2.0
db_block_size=8192
db_files=200
diagnostic_dest=/u01/app/oracle/PROD/diag
_system_trig_enabled=FALSE
sga_target=40960M <<<<<<<<<<<<<<<<<<< HERE is the problem ( 40 GB )
processes=200
db_create_file_dest=/ACFSDUMP/PROD
log_archive_dest_1='location=/ACFSDUMP/PROD'
#No auxiliary parameter file used
*/
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |