Goldengate 12.2 New Feature – Check and validate parameter files using chkprm

In GoldenGate 12.2 we can now validate parameter files before deployment.

There is a new utility called chkprm which can be used for this purpose.’

To run the chkprm utility we provide the name of the parameter file and can optionally indicate what process this parameter file belongs to using the COMPONENT keyword.

Let us look at an example.

ors-db-01@oracle:omprd1>./checkprm ./dirprm/eomprd1.prm --COMPONENT EXTRACT

2016-01-21 21:53:13  INFO    OGG-02095  Successfully set environment variable ORACLE_HOME=/orasw/app/oracle/product/12.1.0/db_1.

2016-01-21 21:53:13  INFO    OGG-02095  Successfully set environment variable ORACLE_SID=omprd2.

2016-01-21 21:53:13  INFO    OGG-02095  Successfully set environment variable TNS_ADMIN=/orasw/app/oracle/product/12.1.0/db_1/network/admin.

2016-01-21 21:53:13  INFO    OGG-02095  Successfully set environment variable NLS_LANG=AMERICAN_AMERICA.AL32UTF8.

(eomprd1.prm) line 13: Parsing error, [DYNAMICRESOLUTION] is deprecated.

(eomprd1.prm) line 22: Parameter [REPORTDETAIL] is not valid for this configuration.

2016-01-21 21:53:13  INFO    OGG-10139  Parameter file ./dirprm/eomprd1.prm:  Validity check: FAIL.

We can see that this parameter file has failed the validation check because we had used this line in the parameter file and REPORTDETAIL is not supported now in 12.2.

STATOPTIONS REPORTDETAIL, RESETREPORTSTATS

We changed the parameter file to include

STATOPTIONS RESETREPORTSTATS

and now run the chkprm utility again. We now see that the verification of the parameter file has completed successfully.

ors-db-01@oracle:BSSTG1>./checkprm ./dirprm/eomprd1.prm

2015-11-18 19:29:45  INFO    OGG-10139  Parameter file ./dirprm/eomprd1.prm:  Validity check: PASS.

Runtime parameter validation is not reflected in the above check.