ORACLE error 20100 in FDPSTP
FDPSTP failed due to ORA-20100: ORA-20100: Temporary file creation for FND_FILE failed.
Directory &FILE_DIR is invalid, contact your system administrator.
Check that the directory is a valid directory with wri06-APR-2016 14:48:29
The concurrent program was unable to write to the specified temporary file because the virtual path assigned to the APPLPTMP environment variable is not referenced in the UTL_FILE_DIR
Read more...
Go to the software location
Copy sample response file from
[oracle@dbaarena ~]$ cp -rfv /u01/11gR2Setup/database/response/ /u01/home
Modify the db_install.rsp file.
oracle.install.option=INSTALL_DB_SWONLY
UNIX_GROUP_NAME=oinstall
INVENTORY_LOCATION=/oracle/OraInventory
ORACLE_HOME=/u01/home/oracle/product/11.2.0/dbhome_1
ORACLE_BASE=/u01/home
oracle.install.db.InstallEdition=EE
oracle.install.db.DBA_GROUP=dba
oracle.install.db.OPER_GROUP=dba
DECLINE_SECURITY_UPDATES=true
Read more...
Use the CREATE RESTORE POINT statement to create a restore point, which is a name associated with an SCN of the database corresponding to the time of the creation of the restore point. A restore point can be used to flash a table or the database back to the time of creation of the restore point without the need to determine the SCN or timestamp.
There are two types of restore point:
• Guaranteed restore points: A guaranteed restore point enables you to flash the database back to the restore point regardless of the DB_FLASHBACK_RETENTION_TARGET initialization parameter setting.
Guaranteed restore points must be dropped explicitly by the user using the DROP RESTORE POINT statement. They do not age out.
• Normal restore points: A normal restore point enables you to flash the database back to a restore point within the time period determined by the DB_FLASHBACK_RETENTION_TARGET initialization parameter. You can explicitly drop a normal restore point using the DROP RESTORE POINT statement.
Read more...
There are reporting programs and data updating programs that need to run either periodically, or on an ad hoc basis. These programs, which run in the background while users continue to work on other tasks are run using the Concurrent Processing architecture. Concurrent Processing is an Oracle E-Business Suite feature that allows these non–interactive and potentially long-running functions to be executed efficiently alongside interactive operations on a specialized server, the Concurrent Processing Server.
Processes that run on the Concurrent Processing server are called Concurrent Requests.
When you submit such a request, either through HTML-based or Forms-based applications, a row is inserted into a database table specifying the program to be run. A Concurrent Manager then reads the applicable requests in the table, and starts the associated concurrent program.
Read more...
