1, test the environment-related replication process, test the data strict requirements of the project.
At the beginning of the environment, you can turn on the handlecollisions parameter run several * period and the day cut processing
You need to close this parameter before the formal test--handlecollisions run several * period and the day cut normal, then carry on the next Test best!
2, process hangs out of the solution
First query the logging information Ggserro.log find out why
Then go to ORACLE/GGS/DIRRPT/RELC1.DSC *.DSC find the corresponding. dsc file to verify the specific cause of the error.
Solve the problem before starting, if it does not start or other reasons cannot start, you can block the corresponding table in the Param, first up and then open the table, and then restart, so that only the corresponding table data problems, other unsynchronized data will also be normal synchronization.
3. Clean up the archive log
Rman Target/
Delete Force Archivelog all completed before ' sysdate-0.5 ';
4. Increase the file method when the table space is insufficient attention to confirm which file
ALTER tablespace ts_index ADD datafile '/oracle/oradata/clctdb/ts_index_02.dbf ' size 5M autoextend on next 10M maxsize 10G ;
5. How to open the archive log
Sqlplus/as SYSDBA
Alter system set open_cursors=1000 Scope=both;
Alter system set processes=1000 Scope=spfile;
Alter system set sessions=1000 Scope=spfile;
Alter system set OPEN_LINKS=50 scope=spfile;
Shutdown immediate
startup Mount;
ALTER DATABASE Archivelog;
--alter system Set db_recovery_file_dest_size = 100G;
ALTER DATABASE open;
Archive log list;
alter system set JOB_QUEUE_PROCESSES=50;
SELECT supplemental_log_data_min from V$database;
ALTER DATABASE ADD supplemental LOG DATA;
Oracle Goldengate Related