22 OGGV-00001 to OGGV-80086
- OGGV-00002
- Compare Pair Key Mapping are invalid
- Category:
- CONFIGURATION
- Cause:
- Compare Pair Key Mapping are invalid
- Action:
- Please check the Column Mapping Tab in Compare Pair Configuration
- OGGV-00003
- Compare Pair Comparison Column Mappings are invalid
- Category:
- BROWSER
- Cause:
- Compare Pair Comparison Column Mappings are invalid
- Action:
- Please check the Column Mapping Tab in Compare Pair Configuration
- OGGV-00004
- Compare Pair Mappings are invalid
- Category:
- BROWSER
- Cause:
- Compare Pair Mappings are invalid
- Action:
- Please check the compare pair mappings tab and address invalid mappings
- OGGV-00005
- Compare Pair Mappings are no longer valid (possible changes in the datasources)
- Category:
- CONFIGURATION
- Cause:
- Compare Pair Mappings are no longer valid (possible changes in the datasources)
- Action:
- Please delete the Compare Pair Mappings and try to create again.
- OGGV-00009
- A Favorite Job/Shortcut with this name already exists. Please choose another name.
- Category:
- Other
- Cause:
- Action:
- OGGV-00010
- Application Error
- Category:
- BROWSER
- Cause:
- Application Error.
- Action:
- Please retry. If the issue persist contact Oracle Support.
- OGGV-00011
- An unexpected error occurred. Please contact the system administrator. Original error message was: {0}
- Category:
- BROWSER
- Cause:
- Unexpected Error.
- Action:
- Please retry. If the issue persist contact Oracle Support.
- OGGV-00012
- An error occurred when trying to update the connection. The operation was not completed.
- Category:
- BROWSER
- Cause:
- An error occurred when trying to update the connection.
- Action:
- Please retry. If the issue persist contact Oracle Support.
- OGGV-00013
- The operation was not completed. Please select a connection to proceed.
- Category:
- BROWSER
- Cause:
- The operation was not completed.
- Action:
- Please select a connection to proceed.
- OGGV-00014
- An error occurred when trying to update the group. The operation was not completed.
- Category:
- BROWSER
- Cause:
- An error occurred when trying to update the group.
- Action:
- Please retry. If the issue persist contact Oracle Support.
- OGGV-00015
- The operation was not completed. Please select a group to proceed.
- Category:
- Other
- Cause:
- The operation was not completed.
- Action:
- Please select a group to proceed.
- OGGV-00016
- The operation was not completed. Please select a profile to proceed.
- Category:
- BROWSER
- Cause:
- The operation was not completed.
- Action:
- Please select a profile to proceed.
- OGGV-00017
- The operation was not completed. Please select a shortcut to proceed.
- Category:
- BROWSER
- Cause:
- The operation was not completed.
- Action:
- Please select a shortcut to proceed.
- OGGV-00018
- Please specify or verify the datasource type.
- Category:
- BROWSER
- Cause:
- Please specify or verify the datasource type.
- Action:
- Please specify or verify the datasource type.
- OGGV-00026
- Specified attribute is not between the expected values of {0} and {1}.
- Category:
- Other
- Cause:
- Action:
- OGGV-00030
- Type specified does not match correct type. Correct type is {1}.
- Category:
- Other
- Cause:
- Action:
- OGGV-00031
- The connection {0} could not be found. Please verify that the name is correct.
- Category:
- Other
- Cause:
- Action:
- OGGV-00032
- A job named {0} already exists. Job name is case insensitive and must be unique.
- Category:
- Other
- Cause:
- Action:
- OGGV-00033
- The profile {0} could not be found. Please verify that the name is correct.
- Category:
- Other
- Cause:
- Action:
- OGGV-00034
- The group {0} could not be found. Please verify that the name is correct.
- Category:
- Other
- Cause:
- Action:
- OGGV-00035
- An error occurred when trying to load metadata information (Indexes) for [{0}]. Connection used was [{1}].
- Category:
- Other
- Cause:
- Action:
- OGGV-00036
- An error occurred when trying to load metadata information (Columns) for [{0}]. Connection used was [{1}].
- Category:
- Other
- Cause:
- Action:
- OGGV-00037
- A connection named {0} already exists. Connection name is case insensitive and must be unique.
- Category:
- Other
- Cause:
- Action:
- OGGV-00038
- A group named {0} already exists. Group name is case insensitive and must be unique.
- Category:
- Other
- Cause:
- Action:
- OGGV-00039
- Finished details will only be available when the entire job finishes.
- Category:
- Other
- Cause:
- Action:
- OGGV-00040
- This compare pair did not complete successfully, therefore the charts will only display the results obtained before the failure.
- Category:
- Other
- Cause:
- Action:
- OGGV-00045
- The job {0} could not be found. Please verify that the name is correct.
- Category:
- Other
- Cause:
- Action:
- OGGV-00048
- You cannot set Compare Pairs status filter to ''{0}'' when run options is ''Review Previous Out-Of-Sync Results''.
- Category:
- Other
- Cause:
- Action:
- OGGV-00056
- GoldenGate Veridata Server could not be reached. Please verify if it is currently running and that your configuration is correct.
- Category:
- Other
- Cause:
- Action:
- OGGV-00058
- Connection to Veridata Server timed out. Please try again.
- Category:
- Other
- Cause:
- Action:
- OGGV-00094
- Connection ''{0}'' still referenced, you cannot delete it.
- Category:
- Other
- Cause:
- Action:
- OGGV-00111
- Tables lookup failed, mgr={0}, port={1}, catalog={2}, schema={3}
- Category:
- Other
- Cause:
- Action:
- OGGV-00112
- Column lookup failed, mgr={0}, port={1}, catalog={2}, schema={3}, table={4}
- Category:
- Other
- Cause:
- Action:
- OGGV-00113
- Index lookup failed, mgr={0}, port={1}, catalog={2}, schema={3}, table={4}
- Category:
- Other
- Cause:
- Action:
- OGGV-00118
- Error Message from Agent: {0}
- Category:
- OTHER
- Cause:
- Errors occured on agent.
- Action:
- Please verify Agent connections and check agent logs to see the error.
- OGGV-00119
- Failed to load the charset: {0}
- Category:
- DATA
- Cause:
- Either the charset name is invalid or the instance of jvm does not support the charset
- Action:
- Please check the charset name or check whether the charset is supported by veridata library.For ICU and Oracle charsets, please check whether veridata library has icu4j-53_1.jar, icu4j-charset-53_1.jar, or orai18n.jar
- OGGV-00121
- Test fault with parameters. int64: 0x{0}, uint64: {1}, int32: {2}, uint32: {3}, int16: {4}, uint16: {5}, int8 {6}, uint8 {7}, char * {8}, char * {9}, char * {10}, char * {11}, char * {12}, void * 0x{13}, double {14}, long double {15}, ptrdiff_t {16}, size_t {17}.
- Category:
- Other
- Cause:
- Action:
- OGGV-00122
- Error Message from {0} Agent: (IPC code = {1}): {2}
- Category:
- OTHER
- Cause:
- Error occured on agent.
- Action:
- Please check agent logs to see the error. IPC code 101 represents a generic VeriAgentException.
- OGGV-00124
- {0} ''{1}'' has changed since it was selected, please try again.
- Category:
- Other
- Cause:
- Action:
- OGGV-00128
- Index validation failed.
- Category:
- BROWSER
- Cause:
- Index validation failed
- Action:
- Check the Column Mapping Tab
- OGGV-00130
- {0} table schema has changed. Please check that the table still exists and column positions and datatypes have not changed.
- Category:
- CONFIGURATION
- Cause:
- Table schema has changed.
- Action:
- Please check that the table still exists and column positions and datatypes have not changed.
- OGGV-00131
- Column mapping is invalid, please check the datatypes and comparison formats.
- Category:
- CONFIGURATION
- Cause:
- Column mapping is invalid.
- Action:
- Please check the datatypes and comparison formats in the Column Mapping Tab.
- OGGV-00134
- Comparison Job ''{0}'' is already running as ({1}, {2}, {3}).
- Category:
- Other
- Cause:
- Action:
- OGGV-00135
- Job ''{0}'' is still running, cannot delete a running job.
- Category:
- Other
- Cause:
- Action:
- OGGV-00136
- Job cannot be run. Check server config parameters server.max_concurrent_jobs and server.max_concurrent_comparision_threads.
- Category:
- DEPLOYMENT
- Cause:
- Job cannot be run.
- Action:
- Check server config parameters server.max_concurrent_jobs and server.max_concurrent_comparision_threads.
- OGGV-00142
- Out of Sync details were not saved for this comparison run
- Category:
- DEPLOYMENT
- Cause:
- Out of Sync details were not saved
- Action:
- Check the directory OOSXML for more information .
- OGGV-00144
- Source column ''{0}'' not found in source table ''{1}''
- Category:
- DEPLOYMENT
- Cause:
- Source column not found in source table
- Action:
- Check the columns in the Column Mapping Tab and verify it with table definition
- OGGV-00145
- Source column ''{0}'' has datatype ''{1}'', the datatype does not match the source table datatype of ''{2}''
- Category:
- CONFIGURATION
- Cause:
- Source column has datatype which does not match with the source table datatype
- Action:
- Check the columns in the Column Mapping Tab and verify it with table definition
- OGGV-00146
- Target column ''{0}'' not found in target table ''{1}''
- Category:
- DEPLOYMENT
- Cause:
- 00146 column not found in target table
- Action:
- Check the columns in the Column Mapping Tab and verify it with table definition
- OGGV-00147
- Target column ''{0}'' has datatype ''{1}'', the datatype does not match the target table datatype of ''{2}''
- Category:
- CONFIGURATION
- Cause:
- Target column has datatype which does not match with the target table datatype
- Action:
- Check the columns in the Column Mapping Tab and verify it with table definition
- OGGV-00148
- The number of source columns does not match the number of target columns
- Category:
- DEPLOYMENT
- Cause:
- The number of source columns does not match the number of target columns
- Action:
- Check the columns in the Column Mapping Tab and verify it with table definition
- OGGV-00149
- The datatype of source column ''{0}'' ({1}) does not match the datatype of target column ''{2}'' ({3})
- Category:
- CONFIGURATION
- Cause:
- The datatype of source column does not match the datatype of target column.
- Action:
- Check the source and target columns in the Column Mapping Tab.
- OGGV-00150
- Source table ''{0}'' does not exist
- Category:
- CONFIGURATION
- Cause:
- Source table does not exist.
- Action:
- Verify the source table.Check the Source Connection configured.
- OGGV-00151
- Target table ''{0}'' does not exist
- Category:
- CONFIGURATION
- Cause:
- Source table does not exist.
- Action:
- Verify the target table.Check the Target Connection configured.
- OGGV-00152
- Source index ''{0}'' does not exist
- Category:
- CONFIGURATION
- Cause:
- Source index does not exist.
- Action:
- Verify the Source table.Check the Source Connection configured.
- OGGV-00153
- Target index ''{0}'' does not exist
- Category:
- CONFIGURATION
- Cause:
- Target index does not exist.
- Action:
- Verify the Target table.Check the Target Connection configured.
- OGGV-00154
- The number of source key columns ({0}) does not match the actual number of columns ({1}) of index ''{2}''
- Category:
- CONFIGURATION
- Cause:
- The number of source key columns does not match the actual number of columns .
- Action:
- Check the columns in the Column Mapping Tab and verify it with table definition.
- OGGV-00155
- The number of target key columns ({0}) does not match the actual number of columns ({1}) of index ''{2}''
- Category:
- CONFIGURATION
- Cause:
- The number of target key columns does not match the actual number of columns .
- Action:
- Check the columns in the Column Mapping Tab and verify it with table definition.
- OGGV-00156
- Source key column ''{0}'' is not part of index ''{1}''
- Category:
- CONFIGURATION
- Cause:
- Source key column is not part of index.
- Action:
- Check the columns in the Column Mapping Tab and verify it with table definition.
- OGGV-00157
- Target key column ''{0}'' is not part of index ''{1}''
- Category:
- CONFIGURATION
- Cause:
- Target key column is not part of index.
- Action:
- Check the columns in the Column Mapping Tab and verify it with table definition.
- OGGV-00158
- The datatype of source key column ''{0}'' ({1}) does not match the datatype of the same column in index ''{2}'' ({3})
- Category:
- CONFIGURATION
- Cause:
- The datatype of source key column does not match the datatype of the same column.
- Action:
- Check the columns in the Column Mapping Tab and verify it with table definition.
- OGGV-00159
- The datatype of target key column ''{0}'' ({1}) does not match the datatype of the same column in index ''{2}'' ({3})
- Category:
- CONFIGURATION
- Cause:
- The datatype of target key column does not match the datatype of the same column.
- Action:
- Check the columns in the Column Mapping Tab and verify it with table definition.
- OGGV-00160
- The number of source keys columns is different than the number of target key columns
- Category:
- CONFIGURATION
- Cause:
- The number of source keys columns is different than the number of target key columns.
- Action:
- Check the columns in the Column Mapping Tab and verify it with table definition.
- OGGV-00161
- The datatype of source key column ''{0}'' ({1}) does not match the datatype of target key column ''{2}'' ({3})
- Category:
- CONFIGURATION
- Cause:
- The datatype of source key column does not match the datatype of target key column.
- Action:
- Check the columns in the Column Mapping Tab and verify it with table definition.
- OGGV-00162
- Index validation failed because there were no mappable columns.
- Category:
- CONFIGURATION
- Cause:
- Index validation failed because there were no mappable columns.
- Action:
- Check the columns in the Column Mapping Tab.
- OGGV-00163
- Enscribe compare pair ''{0}'' cannot be executed because it has user defined keys and sorting is not done in the server.
- Category:
- CONFIGURATION
- Cause:
- Enscribe compare pair cannot be executed because it has user defined keys and sorting is not done in the server.
- Action:
- Please select server sort in Profile and check system defined keys in Column Mapping Tab
- OGGV-00164
- Enscribe compare pair ''{0}'' cannot be executed because the Confirm Out Of Sync step is on.
- Category:
- CONFIGURATION
- Cause:
- Confirm Out Of Sync step is on.
- Action:
- Please uncheck Confirm Out Of Sync in Profile.
- OGGV-00165
- NSK compare pair ''{0}'' cannot be executed because it has delta processing enabled and sorting is not set to ServerSort.
- Category:
- CONFIGURATION
- Cause:
- NSK Sorting setting not set to Server Sort in Profile configuration.
- Action:
- Please set the sorting to ServerSort in Profile configuration and re-run the Job.
- OGGV-00166
- NSK Enscribe compare pair ''{0}'' cannot be executed because it has starting/ending key range(s) when sorting is done in the server.
- Category:
- CONFIGURATION
- Cause:
- NSK Enscribe compare pair cannot be executed because it has starting/ending key range(s) when sorting is done in the server.
- Action:
- Please check the Predicate information in Column Pair Configuration.
- OGGV-00167
- NSK SQL/MP compare pair ''{0}'' cannot be executed because it has SQL predicate(s) when sorting is done in the server.
- Category:
- CONFIGURATION
- Cause:
- NSK SQL/MP compare pair cannot be executed because it has SQL predicate(s) when sorting is done in the server.
- Action:
- Please check the Predicate information in Column Pair Configuration.
- OGGV-00168
- The comparison format of source column ''{0}'' ({1}) cannot convert to the comparison of target column ''{2}'' ({3}).
- Category:
- CONFIGURATION
- Cause:
- The comparison format of source column cannot convert to the comparison of target column.
- Action:
- Please check the Column Mapping Tab.
- OGGV-00170
- Source column ''{0}'': {1} of {2} is greater than the max of {3}.
- Category:
- CONFIGURATION
- Cause:
- Source column ''{0}'': {1} of {2} is greater than the max of {3}.
- Action:
- Please check the Column Mapping Tab.
- OGGV-00171
- Source column ''{0}'': Agent format ''{1}'' does not support ''{2}''.
- Category:
- CONFIGURATION
- Cause:
- Agent format does not support the column.
- Action:
- Please check the Column Mapping Tab.
- OGGV-00172
- Source column ''{0}'' and target column ''{1}'': ''{2}'' is mismatched ({3} and {4}).
- Category:
- CONFIGURATION
- Cause:
- Source column and target column is mismatched.
- Action:
- Please check the Column Mapping Tab.
- OGGV-00173
- The comparison format of source key column ''{0}'' ({1}) cannot convert to the comparison format of target key column ''{2}'' ({3}).
- Category:
- CONFIGURATION
- Cause:
- The comparison format of source key column cannot convert to the comparison format of target key column.
- Action:
- Please check the Column Mapping Tab.
- OGGV-00175
- Row skipped from repair as duplicate row(s) for this key found on Source table.
- Category:
- DATA
- Cause:
- Duplicate records found at Source table.
- Action:
- Remove Duplicate records from source table OR provide an unique column for the table and then map the unique column as Primary Key in Veridata.
- OGGV-00176
- Compare pair ''{0}'' has empty user defined key columns.
- Category:
- CONFIGURATION
- Cause:
- Compare pair ''{0}'' has empty user defined key columns.
- Action:
- Please check the Column Mapping Tab.
- OGGV-00177
- Column was not validated.
- Category:
- CONFIGURATION
- Cause:
- Column was not validated.
- Action:
- Column was not validated.Please use 'Validate Column Mapping' in Compare Pair Configuration.
- OGGV-00179
- The connection type of ''{0}'' cannot be changed to ''{1}''.
- Category:
- Other
- Cause:
- Action:
- OGGV-00180
- The {0} connection type of group ''{1}'' cannot be changed to ''{2}''.
- Category:
- Other
- Cause:
- Action:
- OGGV-00181
- The {0} connection type of job ''{1}'' must match the {2} connection types of all included groups.
- Category:
- Other
- Cause:
- Action:
- OGGV-00188
- Requested sort memory size, {0}m, too large; sort memory set to {1}m
- Category:
- Other
- Cause:
- Action:
- OGGV-00190
- Requested Maximum comparison memory, {0}m, cannot exceed total memory size; maximum comparison memory is set to {1}m
- Category:
- Other
- Cause:
- Action:
- OGGV-00192
- The requested comparison memory {0}m exceeds the configured maximum {1}m
- Category:
- Other
- Cause:
- Action:
- OGGV-00193
- The memory request waiting threshold, {0}, has been exceeded
- Category:
- Other
- Cause:
- Action:
- OGGV-00196
- Agent DBMS type changed: was {0} but is now {1}.
- Category:
- CONFIGURATION
- Cause:
- Agent DBMS type changed.
- Action:
- Please check the Agent information in the Connection Details.
- OGGV-00197
- Partition ''{0}'' was not found.
- Category:
- CONFIGURATION
- Cause:
- Partition ''{0}'' was not found.
- Action:
- Please check the partition information in the Compare Pair Configurations
- OGGV-00198
- {0} Repair Agent failure ''{1}''.
- Category:
- CONFIGURATION
- Cause:
- {0} Repair Agent failure ''{1}''.
- Action:
- Please check the Agent logs for exception stack.If required reach out to Oracle support with the logs.
- OGGV-00199
- Repair is not supported by connection ''{0}''
- Category:
- CONFIGURATION
- Cause:
- Repair is not supported by connection.
- Action:
- Please check the connection DB type and verify.
- OGGV-00202
- Unable to generate out-of-sync chunk file.
- Category:
- OTHER
- Cause:
- Unable to generate out-of-sync chunk file.
- Action:
- Please check whether sufficient disk space is available under reports/oosxml directory and then re-try.
- OGGV-00207
- Repair cannot be executed with Check Update Values set to 'true' when initial comparison skipped the COOS step.
- Category:
- Other
- Cause:
- Action:
- OGGV-00208
- Repair cannot be executed because the Out-Of-Sync file cannot be opened.
- Category:
- Other
- Cause:
- Action:
- OGGV-00209
- Use Secure Socket Layer (SSL) for agent-server communication
- Category:
- Other
- Cause:
- Action:
- OGGV-00226
- Profile/run option {0}(value : {1}) is incompatible with option {2}(value : {3})
- Category:
- Other
- Cause:
- Action:
- OGGV-00227
- Error occurs when running repair job automatically after compare job, error code: {0} error message: {1}
- Category:
- Other
- Cause:
- Action:
- OGGV-00240
- Target column ''{0}'': Agent does not support a comparison format ''{1}'' for datatype ''{2}''.
- Category:
- Other
- Cause:
- Action:
- OGGV-00241
- Target column ''{0}'': {1} of {2} is greater than the max of {3}.
- Category:
- Other
- Cause:
- Action:
- OGGV-00242
- Target column ''{0}'': Agent format ''{1}'' does not support ''{2}''.
- Category:
- Other
- Cause:
- Action:
- OGGV-00246
- Use Source or Target Columns as Key Columns When Generating Compare Pairs
- Category:
- Other
- Cause:
- Action:
- OGGV-00247
- Use All Columns as Key Columns When Generating Compare Pairs
- Category:
- Other
- Cause:
- Action:
- OGGV-00249
- The Job statistics is missing from Veridata Repository for {0}
- Category:
- OTHER
- Cause:
- Errors occured during runtime.
- Action:
- Please check logs to see the error or re-run the job.
- OGGV-00309
- Version mismatch detected: {0} You should press 'Cancel' button to exit and bring Server and Agent to the same version via upgrade or patch. You can still press 'Next' button to proceed, but some features may not work properly.
- Category:
- Other
- Cause:
- Action:
- OGGV-00310
- Version mismatch detected: {0} Some features may not work properly when Server and Agents are on different versions, and you should bring Server and Agents to the same version via upgrade/patch. If you understand and accept the risks, you can still press 'Run Job' button to proceed.
- Category:
- Other
- Cause:
- Action:
- OGGV-00311
- WARNING - Version mismatch detected: {0} Some features may not work properly when Server and Agents are on different versions, and you should bring Server and Agents to the same version via upgrade/patch.
- Category:
- Other
- Cause:
- Action:
- OGGV-00502
- Unable to perform mapping validation. Please select at least one compare pair.
- Category:
- Other
- Cause:
- Action:
- OGGV-00505
- There is already a compare pair named ''{0}'' in group ''{1}''
- Category:
- Other
- Cause:
- Action:
- OGGV-00509
- Delta Processing can not be enabled for the Compare Pair - {0}, Go to Edit Column Mapping -> Delta Processing Tab for performing configuration.
- Category:
- BROWSER
- Cause:
- Delta Processing can not be enabled for the Compare Pair
- Action:
- Go to Edit Column Mapping -> Delta Processing Tab for performing configuration.
- OGGV-00510
- Unable to enable Delta Processing, Please select at least one compare pair.
- Category:
- BROWSER
- Cause:
- Unable to enable Delta Processing.
- Action:
- Please select at least one compare pair.
- OGGV-00511
- Unable to disable Delta Processing, Please select at least one compare pair.
- Category:
- BROWSER
- Cause:
- Unable to disable Delta Processing.
- Action:
- Please select at least one compare pair.
- OGGV-00512
- Delta Processing is already enabled for this Compare Pair - {0}
- Category:
- BROWSER
- Cause:
- Delta Processing is already enabled.
- Action:
- OGGV-00513
- Delta Processing is already disabled for this Compare Pair - {0}
- Category:
- BROWSER
- Cause:
- Delta Processing is already disabled.
- Action:
- OGGV-00514
- To handle duplicate records ensure uniqueness with User-defined keys.
- Category:
- OTHER
- Cause:
- This is a warning when user has tried to override the system generated key mapping. Duplicate rows may not be handled.
- Action:
- Define user keys appropriately such that the keys mapped ensures uniqueness of rows.
- OGGV-00604
- oosxml file error: Out-Of-Sync counts of any column should not be less than Out-Of-Sync count of key column
- Category:
- Other
- Cause:
- Action:
- OGGV-00629
- In group: ''{0}'' , repair pair ''{1}'' completed with error: {2}
- Category:
- Other
- Cause:
- Action:
- OGGV-00650
- CSRF Token is missing or not matching with authorized Session
- Category:
- Other
- Cause:
- Action:
- OGGV-00651
- Config parameter ''truncate_spaces_len'' accepts values of 0 or 1, ignoring ''{0}''
- Category:
- Other
- Cause:
- Action:
- OGGV-00653
- No ComparePairs of selection have out-of-sync in previous run or No previous stats available to generate oosxml for Job: {0}
- Category:
- Other
- Cause:
- Action:
- OGGV-00654
- Encryption bits 'server.encryption.bits' is limited to {0} by the JRE.
- Category:
- Other
- Cause:
- Action:
- OGGV-00658
- Encryption bits 'server.encryption.bits' is required and must be a decimal number
- Category:
- Other
- Cause:
- Action:
- OGGV-00660
- Could not allocate mapped memory for sorting. Using heap memory: {0}
- Category:
- Other
- Cause:
- Action:
- OGGV-00665
- Current changes in the column mapping affects Source Delta Column configuration, Please disable delta processing , complete and save column mapping , then select delta columns from the delta processing tab.
- Category:
- Other
- Cause:
- Action:
- OGGV-00666
- Current changes in the column mapping affects Target Delta Column configuration, Please disable delta processing , complete and save column mapping , then select delta columns from the delta processing tab.
- Category:
- Other
- Cause:
- Action:
- OGGV-00668
- The Veridata Server version {0} is lower than the minimum repository version {1}
- Category:
- Other
- Cause:
- Action:
- OGGV-00669
- The Veridata repository version {0} is lower than the minimum version required by the Veridata Server {1}
- Category:
- Other
- Cause:
- Action:
- OGGV-00670
- Veridata repository connection started with repository version {0}
- Category:
- Other
- Cause:
- Action:
- OGGV-00671
- Veridata repository connection started. The expected repository version is {0} and the actual version is {1}
- Category:
- Other
- Cause:
- Action:
- OGGV-00673
- Repair after compare is not supported for this Job. Please revisit the Profile settings for this Job or uncheck the repair after compare checkbox from Override run options.
- Category:
- Other
- Cause:
- Action:
- OGGV-20001
- Command line flag ''{0}'' is obsolete.
- Category:
- CONFIGURATION
- Cause:
- This flag is no longer in use.
- Action:
- Please check Veridata document to find substitue funciton or flag.
- OGGV-20002
- {0} requires a {1}
- Category:
- CONFIGURATION
- Cause:
- This value is missing.
- Action:
- Please make sure each argument has a value.
- OGGV-20003
- Error reading number ''{0}''
- Category:
- DATA
- Cause:
- This value is not expected.
- Action:
- Please make sure your input is valid
- OGGV-20004
- {0} not allowed with {1}
- Category:
- CONFIGURATION
- Cause:
- An input flag combinaiton is not allowed
- Action:
- Please make your input is valid
- OGGV-20005
- {0} already specified.
- Category:
- CONFIGURATION
- Cause:
- The flag is already specified
- Action:
- Please double check your input flags
- OGGV-20006
- Unrecognized command line flag ''{0}''
- Category:
- CONFIGURATION
- Cause:
- This input flag is not valid.
- Action:
- Please check Veridata document to correct the input flag
- OGGV-20007
- You must specify -job.
- Category:
- CONFIGURATION
- Cause:
- The job flag is missing.
- Action:
- Please add -job or -j to the command line
- OGGV-20009
- Run job command line flags require -job or -j
- Category:
- CONFIGURATION
- Cause:
- The job flag is missing.
- Action:
- Please add -job or -j to the command line
- OGGV-20010
- -g requires -c or -s.
- Category:
- CONFIGURATION
- Cause:
- A group flag requires a compare pair flag, -c, or a status flag, -s
- Action:
- Please add -c or -s to the command line
- OGGV-20011
- -c or -s requires -g.
- Category:
- CONFIGURATION
- Cause:
- A compare pair flag or a status flag requires a groupd flag, -g
- Action:
- Please add -g to the command line
- OGGV-20012
- -rd0 and -rdN require -c.
- Category:
- CONFIGURATION
- Cause:
- A -rd0 or a -rdN flag reuires a compare pair flag, -c
- Action:
- Please add -c to the command line
- OGGV-20013
- You cannot specify ascii/hex keys for SQL tables
- Category:
- DATA
- Cause:
- -pSA/pTA and -pSH/pTH is not valid for SQL/MP
- Action:
- Please provide -pSq/pTq
- OGGV-20014
- -rN requires a number greater than 0
- Category:
- DATA
- Cause:
- -rN flag requires a number greater than 0
- Action:
- Please add a positive number with -rN flag
- OGGV-20016
- The finished stats for record ''{0}'' could not be found
- Category:
- OTHER
- Cause:
- The finished stats for this record could not be found.
- Action:
- Please check whether the delta run id is a valid one or its corresponding finished status exists in veridata db
- OGGV-20018
- Job ''{0}'' not found
- Category:
- DATA
- Cause:
- Veridata cannot find the job.
- Action:
- Please double check whether the job was created before.
- OGGV-20019
- Group ''{0}'' not found
- Category:
- DATA
- Cause:
- Veridata cannot find the group.
- Action:
- Please double check whether the group was created before.
- OGGV-20020
- Compare pair ''{0}'' not found
- Category:
- DATA
- Cause:
- Veridata cannot find the compare pair.
- Action:
- Please double check whether the compare pair was created before.
- OGGV-20021
- Profile ''{0}'' not found
- Category:
- DATA
- Cause:
- Veridata cannot find the profile.
- Action:
- Please double check whether the profile was created before.
- OGGV-20022
- The job {0} is already running with runId {1}
- Category:
- OTHER
- Cause:
- The job is already in running state.
- Action:
- Please wait for the job to be finished.
- OGGV-20025
- No Job Stats found
- Category:
- CONFIGURATION
- Cause:
- No Job Stats found
- Action:
- Check the comparison report files for finished stats . Re run the job and in case the issue persist contact Oracle Support Team.
- OGGV-20050
- Please visit the [Services->Data Sources->VeridataDataSource] Section in \n WebLogic Administration console to reset the Veridata Repository Database password. \n or \n Please contact System administrator for more information.
- Category:
- SECURITY
- Cause:
- Veridata command line tool does not support resetting password
- Action:
- Please visit the [Services->Data Sources->VeridataDataSource] Section in \\n WebLogic Administration console to reset the Veridata Repository Database password. \\n or \\n Please contact System administrator for more information.
- OGGV-20051
- Weblogic User Name required.
- Category:
- CONFIGURATION
- Cause:
- Weblogic User Name is required.
- Action:
- Please enter your weblogic user name.
- OGGV-20052
- Failed to get VericomMBean from veridata server.
- Category:
- OTHER
- Cause:
- An exception was thrown in one of the processes -- getting weblogic user, password, and VericomMBean
- Action:
- Re try again , in case using alias try re creating the alias , use -displayAlias to verify . Sometimes deleting and adding the credential store might be helpful.Make sure to note all the alias if ?deleteCredentialStore option is chosen.Check the documentation for more information.
- OGGV-20053
- Authorization failed to run commandline tools.
- Category:
- SECURITY
- Cause:
- Authorization failed.
- Action:
- Some of your weblogic port, weblogic username, weblogic password are not correct. Please try again.
- OGGV-20054
- An exception, ''{0}'', was thrown in the authentication.
- Category:
- SECURITY
- Cause:
- An exception was thrown in the authentication.
- Action:
- Please search for OGGV-20054 in veridata log to find the root cause
- OGGV-20055
- Waiting for the Job completion with Polling interval {0} sec
- Category:
- Other
- Cause:
- Action:
- OGGV-20056
- User Interrupted
- Category:
- OTHER
- Cause:
- The running job gets user interrupted.
- Action:
- Please try to run the job again.
- OGGV-20066
- You cannot specify SQL partitions for Enscribe
- Category:
- CONFIGURATION
- Cause:
- -pSq/pTq is not valid for Enscribe
- Action:
- Please provide a valid -pSA/pTA or -pSH/pTH
- OGGV-20067
- Provided Job does not support Repair operation , Can use ''{0}'' option to override.
- Category:
- CONFIGURATION
- Cause:
- Provided Job does not support Repair operation.
- Action:
- You could use the flag -norepair to override
- OGGV-20069
- Could not find veridata.cfg location, property veridata.cfg.loc is null. Make sure veridata.cfg.loc property is specified in the vericom script.'
- Category:
- CONFIGURATION
- Cause:
- Could not find veridata.cfg location, property veridata.cfg.loc is null.
- Action:
- Please make sure veridata.cfg.loc property is specified in the vericom script.
- OGGV-20070
- veridata.cfg file does not exist at {0}
- Category:
- CONFIGURATION
- Cause:
- veridata.cfg file does not exist at that path.
- Action:
- Please make sure veridata.cfg file exists at that path.
- OGGV-20072
- Could not find veridata.home location, property veridata.home is null. Make sure veridata.cfg.loc property is specified in the vericom script.
- Category:
- CONFIGURATION
- Cause:
- Could not find veridata.home location, property veridata.home is null.
- Action:
- Plvease make sure veridata.cfg.loc property is specified in the vericom script.
- OGGV-20073
- Veridata home folder does not exist at {0}
- Category:
- CONFIGURATION
- Cause:
- Veridata home folder does not exist at that path.
- Action:
- Please make sure Veridata home folder exists at that path.
- OGGV-20075
- Property ''{0}'' is not present or it has wrong value. Please check veridata.cfg file and provide correct value.
- Category:
- CONFIGURATION
- Cause:
- A property entry is not present or it has wrong value.
- Action:
- Please check veridata.cfg file and provide correct value.
- OGGV-20076
- Failed to get credentail store location. Please check veridata.cfg file and provide correct value.
- Category:
- CONFIGURATION
- Cause:
- Failed to get credentail store location.
- Action:
- Please check veridata.cfg file and provide correct value.
- OGGV-20090
- -s invalid status value.
- Category:
- DATA
- Cause:
- The -s value is not valid.
- Action:
- Please add a valid value with -s flag
- OGGV-30005
- Both host and port must be defined if either is defined for Source
- Category:
- Other
- Cause:
- Action:
- OGGV-30013
- Usage: gg2v [[-noscripting|-create|-replace|-update] -wluser <user> [-wlport <port>]] [-p <propfile>] [-o <out file>] [<extract param file>] <replicat param file> or -help or -version
- Category:
- Other
- Cause:
- Action:
- OGGV-30029
- The option '-wluser' is required when '-noscripting' option not specified
- Category:
- Other
- Cause:
- Action:
- OGGV-30031
- Both host and port must be defined if either is defined for Target
- Category:
- Other
- Cause:
- Action:
- OGGV-40000
- Authorization to allow execution of commandline tools failed.
- Category:
- Other
- Cause:
- Action:
- OGGV-40011
- {0} does not appear to be an encrypted Veridata report file.
- Category:
- Other
- Cause:
- Action:
- OGGV-40012
- Could not generate a new encryption key, check Veridata Server log for errors.
- Category:
- Other
- Cause:
- Action:
- OGGV-50002
- Enter valid XML file name.
- Category:
- FILES
- Cause:
- XML given in command is in-correct or missing from the filepath.
- Action:
- Ensure the name and path of the XML given in command is correct and it exists.
- OGGV-50003
- No operation specified. Operation should be [-create|-update|-replace|-delete |-export]
- Category:
- CONFIGURATION
- Cause:
- Operation [-create|-update|-replace|-delete |-export] not specifed in the command.
- Action:
- Specify the right operation [-create|-update|-replace|-delete |-export] in the command and re-execute it.
- OGGV-50004
- Veridata server is not running. Please start veridata server and rerun the command
- Category:
- OTHER
- Cause:
- Veridata Server is down / not running.
- Action:
- Bring up the Veridata Server and re-run the command.
- OGGV-50005
- Unable to parse xml file
- Category:
- CONFIGURATION
- Cause:
- XML File provided in input is improper.
- Action:
- Ensure all the tags provided in XML us proper and then re-execute it.
- OGGV-50006
- Unable to read config xml file
- Category:
- CONFIGURATION
- Cause:
- Unable to read the XML file provided in input.
- Action:
- Ensure the XML is not opened or locked by other user. Makesure it has proper file permissions set and encodings. Validate the XML and re-run it.
- OGGV-50008
- Error in authenticating with WebLogic, please check the supplied arguments or credentials.
- Category:
- DATA
- Cause:
- Unable to login to weblogic with the credentials passed.
- Action:
- Makesure the weblogic is up and running and the credentials provided is proper.
- OGGV-50009
- Error in executing the scripting request, please contact system administrator for more information.
- Category:
- OTHER
- Cause:
- Error executing import/export script.
- Action:
- Ensure Veridata Server is up and running. Validate the XML and then re-run command.
- OGGV-50010
- Error in reading the supplied xml file.
- Category:
- OTHER
- Cause:
- Unable to read the XML file provided in input.
- Action:
- Ensure the XML is not opened or locked by other user. Makesure it has proper file permissions set and encodings. Validate the XML and re-run it.
- OGGV-50011
- Unknown error during scripting execution, please contact system administrator for more information.
- Category:
- OTHER
- Cause:
- Error executing import/export script.
- Action:
- Ensure Veridata Server is up and running. Validate the XML and then re-run command.
- OGGV-50012
- The supplied WebLogic user does not have required authorization to access command line tools.
- Category:
- CONFIGURATION
- Cause:
- Weblogic User does not have the required access to perform command line operations.
- Action:
- From Weblogic console, provide 'veridataCommandLineUser' role to the user and then restart weblogic and Veridata Server. Later re-execute the command with the same user.
- OGGV-50017
- Cannot connect to database using connection details ''{0}''
- Category:
- NETWORK
- Cause:
- Unable to establish connection with the database
- Action:
- Ensure DB connection details provided in XML is correct. DB is up and running with active listener. Ensure Veridata repository is up and running.
- OGGV-50018
- Connection with the name ''{0}'' already exists.
- Category:
- DATA
- Cause:
- Connection name provided in XML already exists on Veridata.
- Action:
- Provide a different connection name in XML and re-try.
- OGGV-50019
- ComparePair validation failed for Group ''{0}''
- Category:
- DATA
- Cause:
- Compare Pair given in XML does not conform to Veridata Standard.
- Action:
- Ensure the compare-pair has proper column mapping with atleast 1 column as Primary Key.
- OGGV-50020
- Group with the name ''{0}'' already exists.
- Category:
- DATA
- Cause:
- Group name provided in XML already exists on Veridata.
- Action:
- Provide a different group name in XML and re-try.
- OGGV-50021
- Job with the name ''{0}'' already exists.
- Category:
- DATA
- Cause:
- Job name provided in XML already exists on Veridata.
- Action:
- Provide a different Job name in XML and re-try.
- OGGV-50022
- Invalid connection name ''{0}'' is assigned to Group
- Category:
- DATA
- Cause:
- Connection name provided to group in the XML is invalid. Given connection name should already exist in Veridata or in-case of 'create' operation, the connection name should be given in XML in the connection tag before the group creation.
- Action:
- Provide proper connection name in group and re-run the command.
- OGGV-50023
- Invalid group ''{0}'' is assigned to Job
- Category:
- DATA
- Cause:
- Group name provided to Job in the XML is invalid. Given group name should already exist in Veridata or in-case of 'create' operation, the group name should be given in XML in the group tag before the job creation.
- Action:
- Provide proper group name in Job and re-run the command.
- OGGV-50024
- Invalid profile ''{0}'' is assigned to job
- Category:
- DATA
- Cause:
- Profile name provided to Job in the XML is invalid. Given profile name should already exist in Veridata or in-case of 'create' operation, the profile name should be given in XML in the profile tag before the job creation.
- Action:
- Provide proper profile name in Job and re-run the command.
- OGGV-50025
- Invalid profile ''{0}'' is assigned to Compare Pair
- Category:
- DATA
- Cause:
- Profile name provided to compare pair in the XML is invalid. Given profile name should already exist in Veridata or in-case of 'create' operation, the profile name should be given in XML in the profile tag before the compare pair creation.
- Action:
- Provide proper profile name in compare pair and re-run the command.
- OGGV-50026
- Invalid connection name ''{0}'' is assigned to Job
- Category:
- DATA
- Cause:
- Connection name provided to Job in the XML is invalid. Given connection name should already exist in Veridata or in-case of 'create' operation, the connection name should be given in XML in the connection tag before the Job creation.
- Action:
- Provide proper connection name in Job and re-run the command.
- OGGV-50027
- Source pattern ''{0}'' is not well formatted
- Category:
- DATA
- Cause:
- Source Table wildcard pattern given in XML is invalid.
- Action:
- Refer Veridata User Guide for valid/supported patterns and then re-run the command.
- OGGV-50028
- Connection with the name ''{0}'' does not exist.
- Category:
- DATA
- Cause:
- Given connection details in XML does not exist in Veridata.
- Action:
- Provide proper connection details and then re-run the command.
- OGGV-50029
- Group with the name ''{0}'' does not exist.
- Category:
- DATA
- Cause:
- Given group details in XML does not exist in Veridata.
- Action:
- Provide proper group details and then re-run the command.
- OGGV-50030
- Job with the name ''{0}'' does not exist.
- Category:
- DATA
- Cause:
- Given job details in XML does not exist in Veridata.
- Action:
- Provide proper job details and then re-run the command.
- OGGV-50033
- Please enter a valid host name
- Category:
- NETWORK
- Cause:
- Host details provided in connection is invalid.
- Action:
- Ensure the host is reachable with valid port number. Makesure the agent is up and running.
- OGGV-50034
- The catalog ''{0}'' does not exist on the source system
- Category:
- DATA
- Cause:
- Source catalog provided in XML does not exists in Source DB.
- Action:
- Ensure Source DB is up and running. Provide proper catalog details and re-run command.
- OGGV-50035
- The catalog ''{0}'' does not exist on the target system
- Category:
- DATA
- Cause:
- Target catalog provided in XML does not exists in Target DB.
- Action:
- Ensure Target DB is up and running. Provide proper catalog details and re-run command.
- OGGV-50036
- The schema ''{0}'' does not exist on the source system
- Category:
- DATA
- Cause:
- Source schema provided in XML does not exists in Source DB.
- Action:
- Ensure Source DB is up and running. Provide proper schema details and re-run command.
- OGGV-50037
- The schema ''{0}'' does not exist on the target system
- Category:
- DATA
- Cause:
- Target schema provided in XML does not exists in Target DB.
- Action:
- Ensure Target DB is up and running. Provide proper schema details and re-run command.
- OGGV-50038
- The source primary key, ''{0}'', and the target primary key, ''{1}'', must have the same number of columns
- Category:
- DATA
- Cause:
- Number of primary key columns does not match between source and target.
- Action:
- Provide proper/matching primary key columns in XML and then re-run command.
- OGGV-50039
- The target primary key, ''{0}'', requires an index name or a key column list
- Category:
- DATA
- Cause:
- Target Primary Key does not have proper index set in Target DB.
- Action:
- Provide proper primary key.
- OGGV-50040
- The source system requires a catalog name for compare pairs
- Category:
- CONFIGURATION
- Cause:
- Source catalog detail is missing from XML.
- Action:
- Provide source catalog detail in XML and then re-run command.
- OGGV-50041
- The target system requires a catalog name for compare pairs
- Category:
- CONFIGURATION
- Cause:
- Target catalog detail is missing from XML.
- Action:
- Provide target catalog detail in XML and then re-run command.
- OGGV-50042
- The specified index, ''{0}'', does not exist for table ''{1}''
- Category:
- DATA
- Cause:
- Source Primary Key does not have the index defined in Source DB.
- Action:
- Provide proper index details and then re-run command.
- OGGV-50043
- The specified index, ''{0}'', does not exist for table ''{1}''
- Category:
- DATA
- Cause:
- Target Primary Key does not have the index defined in Target DB.
- Action:
- Provide proper index details and then re-run command.
- OGGV-50044
- Unable to create Job ''{0}'' due to: {1}
- Category:
- DATA
- Cause:
- Job creation has failed. Reason for failure will be present in the error message.
- Action:
- Based on the error output, validate the details and then re-run command.
- OGGV-50045
- Unable to create Group ''{0}'' due to: {1}
- Category:
- DATA
- Cause:
- Group creation has failed. Reason for failure will be present in the error message.
- Action:
- Based on the error output, validate the details and then re-run command.
- OGGV-50046
- Unable to create Connection ''{0}'' due to: {1}
- Category:
- DATA
- Cause:
- Connection creation has failed. Reason for failure will be present in the error message.
- Action:
- Based on the error output, validate the details and then re-run command.
- OGGV-50047
- Unable to create Compare Pair ''{0}'' due to: {1}
- Category:
- DATA
- Cause:
- Compare Pair creation has failed. Reason for failure will be present in the error message.
- Action:
- Based on the error output, validate the details and then re-run command.
- OGGV-50048
- Unable to update Job ''{0}'' due to: {1}
- Category:
- DATA
- Cause:
- Job updation has failed.
- Action:
- Based on the error output, validate the details and then re-run command.
- OGGV-50049
- Unable to update Group ''{0}'' due to: {1}
- Category:
- DATA
- Cause:
- Group updation has failed.
- Action:
- Based on the error output, validate the details and then re-run command.
- OGGV-50050
- Unable to update Connection ''{0}'' due to: {1}
- Category:
- DATA
- Cause:
- Connection updation has failed.
- Action:
- Based on the error output, validate the details and then re-run command.
- OGGV-50051
- Unable to update Compare Pair ''{0}'' due to: {1}
- Category:
- DATA
- Cause:
- Compare Pair updation has failed.
- Action:
- Based on the error output, validate the details and then re-run command.
- OGGV-50052
- Unable to delete Group ''{0}'' due to: {1}
- Category:
- DATA
- Cause:
- Group deletion failed. Most likely it will be referred in other Job.
- Action:
- Based on the error output, validate the details and then re-run command.
- OGGV-50053
- Unable to delete Connection ''{0}'' due to: {1}
- Category:
- DATA
- Cause:
- Connection deletion failed. Most likely it will be referred in other Job/Group.
- Action:
- Based on the error output, validate the details and then re-run command.
- OGGV-50054
- Unable to delete Compare Pair ''{0}'' due to: {1}
- Category:
- DATA
- Cause:
- Compare pair deletion failed. Most likely it will be referred in other Group.
- Action:
- Based on the error output, validate the details and then re-run command.
- OGGV-50055
- Connection''{0}'' is used by job ''{1}''
- Category:
- DATA
- Cause:
- Unable to delete connection as it is used by another Job.
- Action:
- Based on the error output, validate the details and then re-run command.
- OGGV-50056
- Connection''{0}'' is used by group ''{1}''
- Category:
- DATA
- Cause:
- Unable to delete connection as it is used by another Group.
- Action:
- Based on the error output, validate the details and then re-run command.
- OGGV-50057
- Group ''{0}'' is used by job ''{1}''
- Category:
- DATA
- Cause:
- Unable to delete group as it is used by another Job.
- Action:
- Based on the error output, validate the details and then re-run command.
- OGGV-50058
- Could not list the existing jobs due to: {0}
- Category:
- DATA
- Cause:
- Unable to delete the Job(s) given in XML.
- Action:
- Based on the error output, validate the details and then re-run command.
- OGGV-50059
- Could not list the existing groups due to: {0}
- Category:
- DATA
- Cause:
- Unable to delete the Group(s) given in XML.
- Action:
- Based on the error output, validate the details and then re-run command.
- OGGV-50061
- Error while parsing the XML {0}
- Category:
- DATA
- Cause:
- Error Reading the given XML
- Action:
- Ensure the tags provided in XML are proper and then re-run command.
- OGGV-50062
- Fatal error while parsing the XML {0}
- Category:
- DATA
- Cause:
- Error Reading the given XML
- Action:
- Ensure the tags provided in XML are proper and then re-run command.
- OGGV-50063
- Missing required value for ''{0}''
- Category:
- DATA
- Cause:
- Mandatory attribute or it's value is missing from XML.
- Action:
- Provide the necessary value for the tag shown in error and re-run command.
- OGGV-50064
- Missing required boolean value for ''{0}''
- Category:
- DATA
- Cause:
- Mandatory boolean attribute or it's value is missing from XML.
- Action:
- Provide the necessary boolean value for the tag shown in error and re-run command.
- OGGV-50065
- Missing required integer value for ''{0}''
- Category:
- DATA
- Cause:
- Mandatory integer attribute or it's value is missing from XML.
- Action:
- Provide the necessary value for the tag shown in error and re-run command.
- OGGV-50066
- Invalid integer value for ''{0}''
- Category:
- DATA
- Cause:
- Given Integer value is wrong in XML for the attribute shown in the error.
- Action:
- Provide the necessary value for the tag shown in error and re-run command.
- OGGV-50101
- Compare Pair ''{0}'' validation failed due to {1}
- Category:
- DATA
- Cause:
- Compare Pair defined in XML does not conform to the Veridata Standard.
- Action:
- Change the comapre pair as per the instructions defined in error message and then re-run command.
- OGGV-50103
- Compare Pair ''{0}'' has multiple partition on ''{1}'' side
- Category:
- CONFIGURATION
- Cause:
- Multiple default Row Partitions have been set
- Action:
- Provide only 1 default row partition and re-run the command.
- OGGV-50104
- Replicat does not have ''{0}'' partition definition, so its considering the matching partition from ''{1}'' side
- Category:
- Other
- Cause:
- Action:
- OGGV-50105
- Exception caught while processing: {0}
- Category:
- CONFIGURATION
- Cause:
- Exception while executing the command.
- Action:
- Ensure Veridata Server is up and running. Veridata repository is reachable. If all the above checks are proper then please contact Oracle Support.
- OGGV-50106
- Usage: veridata_scripting [-create|-update|-replace|-delete] configxml_fullpath [-wlPort portno] -wlUser commandline_username
- Category:
- Other
- Cause:
- Action:
- OGGV-50107
- Connection with the name ''{0}'' has a repairUser but does not have repairPassword or it has a repairPassword but does not have repairUser
- Category:
- CONFIGURATION
- Cause:
- Connection does not have proper repair credentials set in the XML.
- Action:
- Set the Repair details in the XML for that connection.
- OGGV-50108
- Waiting for the Scripting task completion with Polling interval {0} sec
- Category:
- Other
- Cause:
- Action:
- OGGV-50109
- User Interrupted
- Category:
- NETWORK
- Cause:
- User operation has been interrupted.
- Action:
- Ensure Veridata Server is up and running. Veridata repository / Source DB / Target DB is reachable. Check Network connection between server and agents. If all the above checks are proper then please contact Oracle Support.
- OGGV-50110
- Profile with the name ''{0}'' already exists.
- Category:
- DATA
- Cause:
- Profile name given in XML already exists in Veridata Repository and hence it cannot be created again.
- Action:
- Provide a different profile name and re-run the command.
- OGGV-50111
- Profile with the name ''{0}'' does not exist.
- Category:
- DATA
- Cause:
- Profile name given in XML does not exist in Veridata repository and hence cannot be updated.
- Action:
- Create the profile using 'create' option and then re-run the command.
- OGGV-50113
- Unable to delete profile ''{0}'' due to: {1}
- Category:
- DATA
- Cause:
- Unable to delete the profile.
- Action:
- Check if the profile is referred in any other Job/Group. If yes then it needs to be unmapped before deleting it.
- OGGV-50114
- Could not list the existing profiles due to: {0}
- Category:
- NETWORK
- Cause:
- Unable to list the profiles to be deleted.
- Action:
- Check if Veridata Server is up and running, Veridata Repository is reachable and then retry the operation.
- OGGV-50115
- profile''{0}'' is used by job ''{1}''
- Category:
- DATA
- Cause:
- Unable to delete profile as it is referred in another Job.
- Action:
- Unmap the profile from the other Job and then retry.
- OGGV-50116
- profile''{0}'' is used by Compare Pair ''{1}''
- Category:
- DATA
- Cause:
- Unable to delete profile as it is referred in another Compare Pair.
- Action:
- Unmap the profile from the other Compare Pair and then retry.
- OGGV-50123
- Invalid boolean value for ''{0}''. Valid values are true or false.
- Category:
- DATA
- Cause:
- Invalid boolen value is specified in XML. Valid boolean values are true/false
- Action:
- Provide valid value and retry.
- OGGV-50124
- Invalid boolean value ''{0}'' for ''{1}''. Valid values are true or false.
- Category:
- DATA
- Cause:
- Invalid boolen value is specified in XML. Valid boolean values are true/false
- Action:
- Provide valid value and retry.
- OGGV-50125
- Invalid integer value ''{0}'' for ''{1}''
- Category:
- DATA
- Cause:
- Invalid integer value is specified in XML.
- Action:
- Provide valid value and retry.
- OGGV-50126
- Invalid value ''{0}'' for ''{1}''. See documentation for correct set of values.
- Category:
- DATA
- Cause:
- Unsupported ENUM value specified in XML.
- Action:
- Change ENUM value as per documentation and retry.
- OGGV-50127
- Input value ''{0}'' for ''{1}'' is less than minimum supported value of ''{2}''.
- Category:
- DATA
- Cause:
- Value is less than the minimum value supported.
- Action:
- Provide proper value as shown in error message and retry.
- OGGV-50128
- Input value ''{0}'' for ''{1}'' is more than maximum supported value of ''{2}''.
- Category:
- DATA
- Cause:
- Value is more than the maximum value supported.
- Action:
- Provide proper value as shown in error message and retry.
- OGGV-50129
- The parameter ''{0}'' is not supported. Please check documentation for correct parameters.
- Category:
- DATA
- Cause:
- Unknown param provided in XML.
- Action:
- Check documentation for supported params and retry.
- OGGV-50130
- Precision is not supported for ''{0}'' format.
- Category:
- DATA
- Cause:
- Specified datatype format does not support precision.
- Action:
- Change the datatype format or remove precision to continue.
- OGGV-50131
- Scale is not supported for ''{0}'' format.
- Category:
- DATA
- Cause:
- Specified datatype format does not support scale.
- Action:
- Change the datatype format or remove scale to continue.
- OGGV-50132
- Timezone is not supported for ''{0}'' format.
- Category:
- DATA
- Cause:
- Specified datatype format does not support timezone.
- Action:
- Change the datatype format or remove timezone to continue.
- OGGV-50133
- Timezone ''{0}'' is invalid or not supported for ''{1}'' format.
- Category:
- DATA
- Cause:
- Invalid timezone or not supported by the datatype format.
- Action:
- Verify if the specified datatype format supports timezone. If yes, validate the value of timezone.
- OGGV-50134
- Format ''{0}'' is invalid or not supported for ''{1}'' datatype.
- Category:
- DATA
- Cause:
- Invalid format given for the datatype
- Action:
- Refer Veridata documentation for valid type.
- OGGV-50135
- Datatype ''{0}'' is invalid or not supported for ''{1}'' connection
- Category:
- DATA
- Cause:
- Invalid datatype given for the connection
- Action:
- Refer Veridata documentation for valid type.
- OGGV-50138
- Unable to validate delta configuration, There are no valid delta source columns for this compare-pair : ''{0}'', Group Name : ''{1}''
- Category:
- CONFIGURATION
- Cause:
- Invalid column specified as delta column.
- Action:
- Supported delta columns are of type NUMBER / TIMESTAMP. Change the delta column and retry.
- OGGV-50139
- The supplied source delta column : ''{0}'', is not a suitable delta column. Compare-Pair Name : ''{1}'' , Group Name : ''{2}''.
- Category:
- CONFIGURATION
- Cause:
- Invalid column specified as delta column for source.
- Action:
- Supported delta columns are of type NUMBER / TIMESTAMP. Change the delta column and retry.
- OGGV-50140
- Unable to validate delta configuration, There are no valid delta target columns for this compare-pair : ''{0}'', Group Name : ''{1}''
- Category:
- CONFIGURATION
- Cause:
- Invalid column specified as delta column for target.
- Action:
- Supported delta columns are of type NUMBER / TIMESTAMP. Change the delta column and retry.
- OGGV-50141
- The supplied target delta column : ''{0}'', is not a suitable delta column. Compare-Pair Name : ''{1}'' , Group Name : ''{2}''.
- Category:
- CONFIGURATION
- Cause:
- Invalid column specified as delta column.
- Action:
- Supported delta columns are of type NUMBER / TIMESTAMP. Change the delta column and retry.
- OGGV-50142
- The supplied target delta column : ''{0}'', is not a suitable delta column.
- Category:
- CONFIGURATION
- Cause:
- Invalid column specified as delta column for target.
- Action:
- Supported delta columns are of type NUMBER / TIMESTAMP. Change the delta column and retry.
- OGGV-50150
- {0} requires a {1}
- Category:
- DATA
- Cause:
- Required Value Missing.
- Action:
- Refer Veridata Documentation for proper values.
- OGGV-50151
- Error reading number ''{0}''
- Category:
- DATA
- Cause:
- Not a valid number.
- Action:
- Provide valid input and retry.
- OGGV-50152
- {0} not allowed with {1}
- Category:
- CONFIGURATION
- Cause:
- Incorrect flag combination.
- Action:
- Refer Veridata documentation for proper command.
- OGGV-50153
- {0} already specified.
- Category:
- CONFIGURATION
- Cause:
- Flag is already provided in input.
- Action:
- Validate the command and retry.
- OGGV-50154
- Unrecognized command line flag ''{0}''
- Category:
- CONFIGURATION
- Cause:
- Unknown command specified in input.
- Action:
- Refer Veridata documentation for proper command.
- OGGV-50157
- Error in creating supplied output file.
- Category:
- OTHER
- Cause:
- Unable to create the XML File.
- Action:
- Check if proper permissions are set for the directory where file needs to be created. Check for available disk space and then retry.
- OGGV-50158
- Error in writing to supplied output file.
- Category:
- OTHER
- Cause:
- Unable to write to the XML File.
- Action:
- Check if write permissions are set for the file. Ensure that file is not locked/open by any other user. Check for available disk space and then retry.
- OGGV-50159
- Weblogic User Name required.
- Category:
- DATA
- Cause:
- Weblogic username is missing or not provided as input.
- Action:
- Provide weblogic username and then retry.
- OGGV-50160
- Remote repository DB schema and User Name required.
- Category:
- DATA
- Cause:
- Repository details to which data needs to be exported is missing.
- Action:
- Provide repository details and then retry.
- OGGV-50162
- Please re-run the export operation with new valid file or provide permission to overwrite the file.
- Category:
- Other
- Cause:
- Action:
- OGGV-50163
- File does not have write permission. Please provide valid file name.
- Category:
- OTHER
- Cause:
- No write permission set for the file.
- Action:
- Provide valid permission for the file and check if it is not locked by any other user.
- OGGV-50164
- Enscribe type ''{0}'' is not valid.
- Category:
- CONFIGURATION
- Cause:
- Invalid Enscribe Type provided in input.
- Action:
- Refer Veridata documentation for valid enscribe types.
- OGGV-50167
- Side ''{0}'' not recognised
- Category:
- DATA
- Cause:
- Invalid Side given in Input. Valid values are 'S' for Source and 'T' for Target.
- Action:
- Provide valid value and retry.
- OGGV-50170
- Failed to connect to repository. Please check the connection details provided.
- Category:
- OTHER
- Cause:
- Unable to establish connection with Veridata Repository.
- Action:
- Check if repository details provided are Valid. Ensure if the DB is up and running, listener port is open and then retry.
- OGGV-50172
- The connection details provided does not contain veridata tables. Please provide valid veridata repository details and try again.
- Category:
- OTHER
- Cause:
- No Veridata Tables found in the repository.
- Action:
- Check if repository details provided are Valid. Ensure the user has access to Veridata tables and then retry.
- OGGV-50173
- Could not get datasource from spring context.
- Category:
- OTHER
- Cause:
- Datasource is empty.
- Action:
- Ensure Veridata Server is up and running. If not, contact Oracle support.
- OGGV-50174
- Error in getting connection from datasource.
- Category:
- NETWORK
- Cause:
- DB Connection is NULL
- Action:
- Ensure Veridata Server is up and running. Veridata Repository is reachable.
- OGGV-50175
- Repository version of exported veridata repository : ''{0}''.
- Category:
- Other
- Cause:
- Action:
- OGGV-50182
- Error while writing configuration to XML file ''{0}''.
- Category:
- OTHER
- Cause:
- Error writing to XML file.
- Action:
- Check File and directory permissions, file lock(s). Check available disk space and then retry.
- OGGV-50183
- Error while reading configuration XML file ''{0}''.
- Category:
- OTHER
- Cause:
- Error reading from XML file.
- Action:
- Check File and directory permissions, file lock(s). Ensure the XML is valid and then retry.
- OGGV-50186
- Connection list was empty or exporting all connections. No connection name to validate.
- Category:
- Other
- Cause:
- Action:
- OGGV-50187
- Group list was empty or exporting all groups. No group name to validate.
- Category:
- Other
- Cause:
- Action:
- OGGV-50188
- Job list was empty or exporting all jobs. No job name to validate.
- Category:
- Other
- Cause:
- Action:
- OGGV-50189
- Profile list was empty or exporting all profiles. No profile name to validate.
- Category:
- Other
- Cause:
- Action:
- OGGV-50191
- Connection name ''{0}'' is not present in the repository
- Category:
- DATA
- Cause:
- Connection name provided in XML is not present in Veridata Repository.
- Action:
- Provide valid connection and retry.
- OGGV-50193
- Group name ''{0}'' is not present in the repository
- Category:
- DATA
- Cause:
- Group name provided in XML is not present in Veridata Repository.
- Action:
- Provide valid group and retry.
- OGGV-50195
- Job name ''{0}'' is not present in the repository
- Category:
- DATA
- Cause:
- Job name provided in XML is not present in Veridata Repository.
- Action:
- Provide valid Job and retry.
- OGGV-50197
- Profile name ''{0}'' is not present in the repository
- Category:
- DATA
- Cause:
- Profile name provided in XML is not present in Veridata Repository.
- Action:
- Provide valid Profile and retry.
- OGGV-50198
- Connection option not provided for exporting. Not exporting any independent connection objects.
- Category:
- Other
- Cause:
- Action:
- OGGV-50199
- Group option not provided for exporting. Not exporting any independent group objects.
- Category:
- Other
- Cause:
- Action:
- OGGV-50200
- Job option not provided for exporting. Not exporting any independent job objects.
- Category:
- Other
- Cause:
- Action:
- OGGV-50201
- Profile option not provided for exporting. Not exporting any independent profile objects.
- Category:
- Other
- Cause:
- Action:
- OGGV-50217
- Failed to export connections.
- Category:
- OTHER
- Cause:
- Unable to export connections to XML
- Action:
- Check if Veridata Server is up and running. Veridata repository is reachable. XML has proper file permissions set. Required disk space is available.
- OGGV-50218
- Failed to export groups.
- Category:
- OTHER
- Cause:
- Unable to export groups to XML.
- Action:
- Check if Veridata Server is up and running. Veridata repository is reachable. XML has proper file permissions set. Required disk space is available.
- OGGV-50219
- Failed to export jobs.
- Category:
- OTHER
- Cause:
- Unable to export jobs to XML
- Action:
- Check if Veridata Server is up and running. Veridata repository is reachable. XML has proper file permissions set. Required disk space is available.
- OGGV-50220
- Failed to export profiles.
- Category:
- OTHER
- Cause:
- Unable to export profiles to XML
- Action:
- Check if Veridata Server is up and running. Veridata repository is reachable. XML has proper file permissions set. Required disk space is available.
- OGGV-50222
- The connection url ''{0}'' is unrecognized. URLs need to start with one of ''{1}}''.
- Category:
- DATA
- Cause:
- Invalid JDBC URL Provided.
- Action:
- Refer Veridata documentation for valid url's.
- OGGV-50223
- Jdbc driver class ''{0}'' not found in the classpath.
- Category:
- DEPLOYMENT
- Cause:
- Missing JDBC Driver.
- Action:
- Add the JDBC driver in the classpath and retry.
- OGGV-50224
- NSK file-pattern is not supported with schema wildcard. Please use exact names with file-pattern options.
- Category:
- DATA
- Cause:
- NSK file-pattern is not supported with schema wildcard.
- Action:
- Please use exact names with file-pattern options.
- OGGV-50225
- 'colfilter' is not valid for filter type exclude
- Category:
- CONFIGURATION
- Cause:
- 'colfilter' is not valid for filter type exclude
- Action:
- Refer Veridata documentation for valid types.
- OGGV-50234
- Argument 'vdtPath' is only for export operation when using external veridata db and using 'exportPassword' argument.
- Category:
- CONFIGURATION
- Cause:
- Wrong usage of arguments.
- Action:
- Refer Veridata documentation for proper usage of arguments.
- OGGV-50237
- External veridata installation path is null. Path is required for exporting password for external veridata installation.
- Category:
- DATA
- Cause:
- External veridata installation path is null. Path is required for exporting password for external veridata installation.
- Action:
- Specify proper veridata installation path and retry.
- OGGV-50238
- External veridata installation path ''{0}'' does not exist or is incorrect. Please enter correct path for external veridata installation.
- Category:
- DATA
- Cause:
- External veridata installation path specified does not exist or is incorrect. Please enter correct path for external veridata installation.
- Action:
- Specify proper veridata installation path and retry.
- OGGV-50241
- Path ''{0}'' does not exist.
- Category:
- DATA
- Cause:
- Specified jps path does not exist or jps-config-jse.xml is missing in that path.
- Action:
- Specify proper path, check if jps-config-jse.xml exists in that path and has proper permissions set.
- OGGV-50242
- Jps file was not found in the path ''{0}''. Please enter the correct veridata installtion path. It will be domain path for 12c and Installation location for 11g.
- Category:
- DATA
- Cause:
- Specified jps path does not exist or jps-config-jse.xml is missing in that path.
- Action:
- Specify proper path, check if jps-config-jse.xml exists in that path and has proper permissions set.
- OGGV-50244
- Could not find java.home from system property.
- Category:
- OTHER
- Cause:
- Java home is not set.
- Action:
- Ensure Proper Java is installed and JAVA_HOME is set.
- OGGV-50246
- Java home ''{0}'' does not exist.
- Category:
- OTHER
- Cause:
- Java home is not set.
- Action:
- Ensure Proper Java is installed and JAVA_HOME is set.
- OGGV-50248
- Failed to export connection password to file.
- Category:
- OTHER
- Cause:
- Failed to export credentials to the file.
- Action:
- Ensure Veridata Server is up and running. Veridata repository is reachable. XML has proper permissions set. Required disk space ia available.
- OGGV-50250
- Failed to read passwords from wallet.
- Category:
- OTHER
- Cause:
- Unable to read credentials from Wallet.
- Action:
- Ensure Veridata Server is up and running. Wallet is not corrupted and then retry.
- OGGV-50251
- Wrong number of arguments passed for wallet export operation.
- Category:
- CONFIGURATION
- Cause:
- Invalid / Missing arguments passed for export operation.
- Action:
- Refer Veridata documentation.
- OGGV-50252
- Wrong argument passed ''{0}''
- Category:
- CONFIGURATION
- Cause:
- Invalid / Missing arguments passed for export operation.
- Action:
- Refer Veridata documentation.
- OGGV-50253
- The source system requires a schema name for compare pairs
- Category:
- CONFIGURATION
- Cause:
- Source Schema is missing in Input.
- Action:
- Provide Source schema and then retry.
- OGGV-50254
- The target system requires a schema name for compare pairs
- Category:
- CONFIGURATION
- Cause:
- Target Schema is missing in Input.
- Action:
- Provide Target schema and then retry.
- OGGV-50255
- Veridata path provided ''{0}'' does not exist.
- Category:
- DATA
- Cause:
- Veridata path does not exists.
- Action:
- Specify proper path. Ensure proper permissions are set for the directory.
- OGGV-50256
- Veridata path ''{0}'' should be a directory.
- Category:
- DATA
- Cause:
- Veridata Path provided is not a directory.
- Action:
- Specify proper path. Ensure proper permissions are set for the directory.
- OGGV-50257
- "vdtPath" argument is missing. Exporting password for external Veridata setup requires 'vdtPath' argument as well.
- Category:
- CONFIGURATION
- Cause:
- Missing argument 'vdtPath'
- Action:
- Refer Veridata documentation.
- OGGV-50258
- Unable to validate delta configuration, Both Source and Target Delta Queries can not be Null for this compare-pair : ''{0}'', Group Name : ''{1}''
- Category:
- DATA
- Cause:
- Delta queries are null
- Action:
- Provide valid delta columns and queries and retry.
- OGGV-50259
- Unable to validate delta configuration, Source Delta Query required for this compare-pair : ''{0}'', Group Name : ''{1}''
- Category:
- DATA
- Cause:
- Source delta query is null
- Action:
- Provide valid delta columns and queries and retry.
- OGGV-50260
- Unable to validate delta configuration, Target Delta Query required for this compare-pair : ''{0}'', Group Name : ''{1}''
- Category:
- DATA
- Cause:
- Target delta query is null
- Action:
- Provide valid delta columns and queries and retry.
- OGGV-50261
- No operation specified. Operation should be [-export]
- Category:
- CONFIGURATION
- Cause:
- Invalid / Missing operation 'export'
- Action:
- Refer Veridata Documentation.
- OGGV-50262
- No operation specified. Operation should be [-create | -update | -delete | -replace]
- Category:
- CONFIGURATION
- Cause:
- No operation specified. Operation should be [-create | -update | -delete | -replace]
- Action:
- Refer Veridata Documentation.
- OGGV-50263
- Operation ''{0}'' not allowed for profile ''{1}''. Only update operation is allowed for default profile.
- Category:
- CONFIGURATION
- Cause:
- Invalid operation set for default profile. Only update operation is allowed for default profile
- Action:
- Only update operation is allowed for default profile
- OGGV-50264
- Target pattern ''{0}'' is not well formatted
- Category:
- DATA
- Cause:
- Invalid Target Pattern.
- Action:
- Validate the target pattern and then retry.
- OGGV-50265
- Unable to delete Job ''{0}'' due to: {1}
- Category:
- CONFIGURATION
- Cause:
- Unable to delete Job.
- Action:
- Ensure Veridata Server is up and running. Do the changes based on the error message and then retry.
- OGGV-50267
- Invalid Param option ''{0}'' present for Connection ''{1}''.
- Category:
- CONFIGURATION
- Cause:
- Invalid param option provided for connection.
- Action:
- Refer Veridata Documentation.
- OGGV-50268
- Table name should be present if partition pair is not available
- Category:
- CONFIGURATION
- Cause:
- Table name should be present if partition pair is not available
- Action:
- Add the table name attribute in table-partition tag in xml.
- OGGV-60003
- Veridata Agent shutting down on port {0} due to error: {1}
- Category:
- CONFIGURATION
- Cause:
- Agent Port might be in use OR insufficient memory allocated for Agent OR application error.
- Action:
- Check if any other application is using the same Agent Port. If yes, configure a different port in agent.properties.\n" + " If Agent has gone down due to insufficient memory, then allocate more memory for Veridata Agent and Restart Agent. \n" + " If issue is something else then, please contact Oracle Support.
- OGGV-60005
- Could not find the agent properties file ''{0}''
- Category:
- DEPLOYMENT
- Cause:
- agent.properties file is missing from the Agent deployed location.
- Action:
- Check if agent.properties file exists in Agent deployed location. If the file does not exists then try redeploying the agent again.
- OGGV-60006
- Error reading file ''{0}'': {1}
- Category:
- FILES
- Cause:
- Unable to read agent.properties file from the Agent deployed location due to permission issue or memory issue in Agent.
- Action:
- Check if agent.properties file has proper read permissions set. If any issue w.r.t memory then, allocate sufficient memory for Agent and restart the application.
- OGGV-60007
- Character set conversion error: {0}
- Category:
- CONFIGURATION
- Cause:
- Failed as the application is unable to convert the input String to given encoding format.
- Action:
- Set the column format to 'binary' in Veridata. Also map such columns as a hash column in Veridata.
- OGGV-60008
- The database.url property is required.
- Category:
- CONFIGURATION
- Cause:
- The database.url key is missing or does not have any value set in agent.properties
- Action:
- Specify the JDBC url for key 'database.url' and restart Agent.
- OGGV-60009
- The database.url ''{0}'' is unrecognized. URLs need to start with one of ''{{1}}''.
- Category:
- CONFIGURATION
- Cause:
- The JDBC url given for key 'database.url' in agent.properties is invalid.
- Action:
- Provide proper JDBC url and restart Agent.
- OGGV-60012
- IO Error encountered: {0}
- Category:
- NETWORK
- Cause:
- Application failed to process the data stream. Can be due to insufficient memory or network issue.
- Action:
- Ensure proper memory is available for agent. Also check Database and Veridata Server are up and running and then restart Agent.
- OGGV-60013
- Unhandled exception ''{0}'': {1}
- Category:
- OTHER
- Cause:
- Agent failed to process the data stream.
- Action:
- Contact Oracle Support.
- OGGV-60015
- Missing value for: {0}
- Category:
- OTHER
- Cause:
- Mandatory value is missing in the data chunks.
- Action:
- Contact Oracle Support.
- OGGV-60016
- Parsing exception: {0}
- Category:
- OTHER
- Cause:
- Invalid data chunk.
- Action:
- Contact Oracle Support.
- OGGV-60017
- Parsing warning: {0}
- Category:
- OTHER
- Cause:
- Data chunks received might not conform to the standard.
- Action:
- This should not stop the application from functioning properly and can be ignored.
- OGGV-60018
- Unexpected type: {0}
- Category:
- DEPLOYMENT
- Cause:
- It can happen when there is a mismatch between Agent and Server versions.
- Action:
- Ensure both Agent and Veridata Server are on the same versions. Even with the same versions if this issue occurs then contact Oracle Support.
- OGGV-60019
- Corrupted row encountered: {0}
- Category:
- OTHER
- Cause:
- Invalid OOS data.
- Action:
- Ensure sufficient disk space is available in Server for storing sorted data. With ample disk space on server if this issue occurs then contact Oracle Support.
- OGGV-60020
- Record length exceeds bytes remaining in message
- Category:
- OTHER
- Cause:
- Invalid OOS data.
- Action:
- Ensure sufficient disk space is available in Server for storing sorted data. With ample disk space on server if this issue occurs then contact Oracle Support.
- OGGV-60021
- Row length exceeds bytes remaining in message
- Category:
- OTHER
- Cause:
- Invalid OOS data.
- Action:
- Ensure sufficient disk space is available in Server for storing sorted data. With ample disk space on server if this issue occurs then contact Oracle Support.
- OGGV-60024
- Failed to open data source for user {0} (from {1} host)
- Category:
- CONFIGURATION
- Cause:
- Invalid Database credentials given as input.
- Action:
- Provide proper database credentials in Veridata Connection.
- OGGV-60025
- User ''{0}'' could not connect to database: {1}
- Category:
- NETWORK
- Cause:
- Unable to connect to database.
- Action:
- Check if database is up and running | DB listeners and ports are open for the Agent to access | Verify DB credentials provided in Veridata connection.
- OGGV-60026
- Could not get schemas: {0}
- Category:
- DATA
- Cause:
- Unable to access database schema(s).
- Action:
- Ensure DB is up and running and Given DB Schema exists and the DB user given in Veridata connection has access to this schema.
- OGGV-60027
- Could not get tables: {0}
- Category:
- DATA
- Cause:
- Unable to access database tables.
- Action:
- Ensure DB is up and running and Given DB table exists and the DB user given in Veridata connection has access to this table.
- OGGV-60028
- Could not get database version: {0}
- Category:
- NETWORK
- Cause:
- Unable to read version of the database
- Action:
- Check if database is up and running | DB listeners and ports are open for the Agent to access | Verify DB credentials provided in Veridata connection.
- OGGV-60029
- Could not get metadata for ''{0}'': {1}
- Category:
- DATA
- Cause:
- Could not read database.
- Action:
- Ensure DB is up and running and Given DB table/schema exists and the DB user given in Veridata connection has access to this table/schema.
- OGGV-60030
- Could not get index metadata for ''{0}'': {1}
- Category:
- DATA
- Cause:
- Could not read database Index.
- Action:
- Ensure DB is up and running and Given DB table/schema exists and the DB user given in Veridata connection has access to this table/schema.
- OGGV-60031
- Could not list catalogs: {1}
- Category:
- DATA
- Cause:
- Unable to read Database catalog.
- Action:
- Ensure DB is up and running and Given DB catalog exists and the DB user given in Veridata connection has access to this catalog.
- OGGV-60032
- Could not execute statement <{0}>: {1}
- Category:
- DATA
- Cause:
- Unable to run queries on database.
- Action:
- Ensure DB is up and running and User given in connection configuration has access to run the query on the specified table. If all details are proper and still issue occurs then contact Oracle Support.
- OGGV-60033
- Table ''{0}'' not found
- Category:
- DATA
- Cause:
- Table does not exists in database.
- Action:
- Ensure that table exists in database and the user given in connection configuration has access to that table.
- OGGV-60034
- Could not convert value to a String: {0}
- Category:
- CONFIGURATION
- Cause:
- Occurs when special characters exists in database and is not conformed to UTF-8 encoding standard.
- Action:
- Ensure to keep the Veridata compare format to 'binary' mode and mark the column as Hash column in Veridata.
- OGGV-60035
- Could not convert value to a number: {0}
- Category:
- DATA
- Cause:
- Invalid number obtained from Table.
- Action:
- Validate the number is proper in database. If proper, contact Oracle Support.
- OGGV-60036
- Could not get type info: {0}
- Category:
- OTHER
- Cause:
- Could not read the information of datatypes supported by the database.
- Action:
- Ensure DB and listener service is up and running and the user has access to the database.
- OGGV-60038
- Database query failed: ''{1}'' SQL<{0}>
- Category:
- OTHER
- Cause:
- Unable to execute the query in database.
- Action:
- Ensure DB and listener service is up and running and the user has access to the table. Contact Oracle support if all details are proper.
- OGGV-60039
- COOS lookup query failed: ''{1}'' SQL<{0}>
- Category:
- OTHER
- Cause:
- Unable to execute the query in database.
- Action:
- Ensure DB and listener service is up and running and the user has access to the table. Contact Oracle support if all details are proper.
- OGGV-60040
- The specified transaction isolation level, ''{0}'', is not recognized
- Category:
- CONFIGURATION
- Cause:
- Issue occurs when Isolation level is not [Read Committed | Read Uncommitted | Snapshot].
- Action:
- Ensure proper Isolation level is set in agent.properties for key 'database.transaction.isolation' and restart agent. The comments section in agent.properties has more details on which Isolation level to be set based on the underlying database.
- OGGV-60041
- The specified transaction isolation level, ''{0}'', is not support for {1} databases
- Category:
- CONFIGURATION
- Cause:
- Warning shown when Isolation level set in agent.properties is not supported by the underlying database.
- Action:
- Ensure proper Isolation level is set in agent.properties for key 'database.transaction.isolation' and restart agent. The comments section in agent.properties has more details on which Isolation level to be set based on the underlying database.
- OGGV-60042
- The length of column ''{0}'', {1}, exceeds the supported maximum length, {2}
- Category:
- DATA
- Cause:
- Length of the data present in the database exceeds the max length supported by the column.
- Action:
- Change the column format to 'binary' in Veridta and re-run the comparison.
- OGGV-60043
- The display value of hash column ''{0}'' was truncated to {1} bytes
- Category:
- Other
- Cause:
- Action:
- OGGV-60044
- An unexpected exception has occurred: {0}
- Category:
- NETWORK
- Cause:
- Database not responding or shutdown unexpectedly.
- Action:
- Ensure DB and listener service is up and running and re-run comparison.
- OGGV-60046
- A catalog is required
- Category:
- CONFIGURATION
- Cause:
- Catalog value is missing in the Input.
- Action:
- Provide proper Catalog value.
- OGGV-60048
- Database metadata request failed: {0}
- Category:
- NETWORK
- Cause:
- Unable to get the Database Metadata.
- Action:
- Ensure DB and listener service is up and running and User has the required access to the database being queried.
- OGGV-60049
- Could not load database driver ''{0}''
- Category:
- CONFIGURATION
- Cause:
- JDBC driver specified in agent.properties is missing.
- Action:
- Ensure proper value is set for the key 'server.jdbcDriver' in agent.properties and the driver exists in the 'drivers' directory of the Agent.
- OGGV-60050
- The connection cache property ''{0}'' has been set to ''{1}''.
- Category:
- Other
- Cause:
- Action:
- OGGV-60051
- You must login before getting ''{0}''
- Category:
- NETWORK
- Cause:
- Database session closed.
- Action:
- Ensure DB and listener service is up and running and User has the required access to the database.
- OGGV-60052
- Comparison format ''{0}'' is not supported on ''{1}''
- Category:
- CONFIGURATION
- Cause:
- Contact Oracle Support.
- Action:
- Contact Oracle Support.
- OGGV-60053
- Repair fetch query failed: ''{1}'' SQL<{0}>
- Category:
- OTHER
- Cause:
- Unable to run repair in the database.
- Action:
- Ensure DB and listener service is up and running and User has repair access to the database.
- OGGV-60054
- Lookup failed during apply: ''{0}''
- Category:
- NETWORK
- Cause:
- Unable to run repair in the database.
- Action:
- Ensure DB and listener service is up and running and User has repair access to the database.
- OGGV-60055
- Fetch of long varchar/varbinary returned 0 rows.
- Category:
- NETWORK
- Cause:
- Unable to fetch long/raw/binary data from the database.
- Action:
- Ensure DB and listener service is up and running and User has repair access to the database.
- OGGV-60056
- Repair apply failed: ''{0}''
- Category:
- NETWORK
- Cause:
- Unable to run repair in the database.
- Action:
- Ensure DB and listener service is up and running and User has repair access to the database.
- OGGV-60058
- Unexpected tag: {0}
- Category:
- DEPLOYMENT
- Cause:
- Unexpected value in the data chunk. It can happen when the Agent and Veridata Server versions are different.
- Action:
- Ensure to have both Agent and Server on same versions before running comparison. Even with same versions if issue occurs then contact Oracle Support.
- OGGV-60059
- Could not configure XML output: {0}
- Category:
- DEPLOYMENT
- Cause:
- Unable to parse the data chunk. It can happen when the Agent and Veridata Server versions are different OR sufficient memory is not set for the Application to process the data.
- Action:
- Ensure to have both Agent and Server on same versions and also allocate sufficient memory before running comparison.
- OGGV-60060
- The side, ''{0}'', specified in the request does not match the side specified in the login request
- Category:
- OTHER
- Cause:
- Can be ignored.
- Action:
- Can be ignored.
- OGGV-60063
- Ignoring conversion exception: {0}
- Category:
- OTHER
- Cause:
- Can be Ignored.
- Action:
- Can be Ignored.
- OGGV-60064
- Duplicate key found
- Category:
- DATA
- Cause:
- Occurs when duplicate data exists in database. Usually occurs when no primary/unique key constraint is set in database.
- Action:
- Can be Ignored.
- OGGV-60065
- Caught unexpected SQL exception: {0} retry= {1}
- Category:
- NETWORK
- Cause:
- Exception while running repair on database.
- Action:
- Ensure DB and listener service is up and running and User has repair access to the database.
- OGGV-60066
- CLOB I/O error: {0}
- Category:
- OTHER
- Cause:
- Unable to set repait value for LOB types during repair.
- Action:
- Ensure DB and listener service is up and running and User has repair access to the database.
- OGGV-60067
- Error freeing temporary CLOB: {}
- Category:
- OTHER
- Cause:
- Unable to release memory for LOB types.
- Action:
- Ensure sufficient memory is avaiable for Agent and restart Agent. Also makesure that DB and listener services are active.
- OGGV-60068
- Could not set the Session Time Zone to {0}
- Category:
- DATA
- Cause:
- Unable to set session timezone for Oracle Database.
- Action:
- Contact DBA.
- OGGV-60069
- Ignoring invalid database hint: {0}
- Category:
- CONFIGURATION
- Cause:
- Invalid Oracle Hint set as Input.
- Action:
- Provide proper value for Oracle Hint in the Profile configuration before running comparison.
- OGGV-60070
- Character encoding exception: {0}
- Category:
- CONFIGURATION
- Cause:
- Character encoding not supported. Can happen when special characters exists in database.
- Action:
- Set the column format to 'binary' and make the column as Hash column and then run comparison.
- OGGV-60074
- Request was unexpectedly interrupted
- Category:
- NETWORK
- Cause:
- Agent application is interrupted.
- Action:
- Check if the DB and listeners are up and running. Check if Veridata Server is up.
- OGGV-60075
- A getConnection() request was interrupted
- Category:
- NETWORK
- Cause:
- Can occur if the DB went down or is not responding or has reached the max DB connection limit.
- Action:
- Ensure DB and listener services are up and running. Check the active DB connections. If connection limit is reached then try increasing the DB connection limit.
- OGGV-60076
- Cannot parse the database exception error code "{0}", expecting integer
- Category:
- CONFIGURATION
- Cause:
- Invalid error codes specified for key 'database.additional.repair.warnings' in agent.properties.
- Action:
- Provide error codes in Number format for key 'database.additional.repair.warnings' and restart Agent.
- OGGV-60077
- Type name ''{0}'' java.sql.Types value ''{1}'' defaulting to BLOB type
- Category:
- Other
- Cause:
- Action:
- OGGV-60078
- Repair apply failed: code: {0}, msg: ''{1}''
- Category:
- DATA
- Cause:
- Error applying repair on Database.
- Action:
- Ensure DB and listener services are up and running. Check the user has repair privileges for the tables.
- OGGV-60080
- Could not get position for column ''{0}'' in table ''{1}'' for index ''{2}''
- Category:
- OTHER
- Cause:
- Could not read column index from table.
- Action:
- Ensure DB and listener services are up and running. Check the column indexing has been set at database and the user has the right priviliges to read the indexes.
- OGGV-60081
- Veridata agent will not use kerberos to access this datasource. The entry ''{0}'' cannot be found in agent.properties file or is given an empty value
- Category:
- Other
- Cause:
- Action:
- OGGV-60082
- Veridata agent will not use kerberos to access this datasource. The kerberos file ''{0}'' cannot be found in veridata agent root directory
- Category:
- Other
- Cause:
- Action:
- OGGV-60153
- Expected {0} type to be {1}
- Category:
- DATA
- Cause:
- Invalid datatype in data chunk.
- Action:
- Contact Oracle Support.
- OGGV-60154
- SQL exception occurred during UDT lookup of {0}, msg: {1}
- Category:
- DATA
- Cause:
- Application Error.
- Action:
- Contact Oracle Support.
- OGGV-60155
- Field {0} not found in UDT {1}
- Category:
- DATA
- Cause:
- Array UDT types are missing for Oracle Database.
- Action:
- Contact Oracle Support.
- OGGV-60156
- Field {0} expected type {1}, got {2}
- Category:
- OTHER
- Cause:
- Invalid datatype in data chunk.
- Action:
- Contact Oracle Support.
- OGGV-60157
- Field {0} was missing value.
- Category:
- OTHER
- Cause:
- Invalid datatype in data chunk.
- Action:
- Contact Oracle Support.
- OGGV-60158
- Unable to serialize: {0}, msg: {1}
- Category:
- OTHER
- Cause:
- Unable to serialize the data chunk.
- Action:
- Contact Oracle Support.
- OGGV-60159
- Unable to deserialize: {0}, msg: {1}
- Category:
- CONFIGURATION
- Cause:
- Unable to deserialize the data chunk.
- Action:
- Contact Oracle Support.
- OGGV-60163
- Agent communications error: {0}
- Category:
- NETWORK
- Cause:
- Agent connection did not shutdown gracefully.
- Action:
- Can be ignored.
- OGGV-60164
- Query to get the delta-base value, failed: ''{1}'' SQL<{0}>
- Category:
- CONFIGURATION
- Cause:
- Invalid delta query.
- Action:
- Specify proper delta query in the delta configuration tab and re-run comparison.
- OGGV-60165
- Invalid delta-base value-query, result set.
- Category:
- CONFIGURATION
- Cause:
- Invalid delta query.
- Action:
- Specify proper delta query in the delta configuration tab. Verify user has right privileges to access the table and then re-run comparison.
- OGGV-60166
- No valid rows on delta base value-query, result set.
- Category:
- CONFIGURATION
- Cause:
- Invalid delta query.
- Action:
- Specify proper delta query in the delta configuration tab. Verify user has right privileges to access the table and then re-run comparison.
- OGGV-60167
- More than one rows in delta base value-query, result set.
- Category:
- CONFIGURATION
- Cause:
- Invalid delta query.
- Action:
- Specify proper delta query in the delta configuration tab and then re-run comparison.
- OGGV-60168
- More than one column in delta base value-query, result set.
- Category:
- CONFIGURATION
- Cause:
- Invalid delta query.
- Action:
- Specify proper delta query in the delta configuration tab and then re-run comparison.
- OGGV-60169
- More than one result-set in delta base value-query, result.
- Category:
- CONFIGURATION
- Cause:
- Invalid delta query
- Action:
- Specify proper delta query in the delta configuration tab and then re-run comparison.
- OGGV-60170
- Unable to get the delta base value from the query.
- Category:
- CONFIGURATION
- Cause:
- Invalid delta query.
- Action:
- Specify proper delta query in the delta configuration tab. Verify user has right privileges to access the table and then re-run comparison.
- OGGV-60171
- Unable to convert Oracle number {1}
- Category:
- DATA
- Cause:
- Invalid Number obtained in database.
- Action:
- Validate the data in database and then re-run comparison.
- OGGV-60174
- The input of the property, {0}, is not a valid number, {1}
- Category:
- DATA
- Cause:
- Invalid Number obtained in agent property file.
- Action:
- Validate the property input in agent.properties
- OGGV-60175
- Row skipped from repair as duplicate row(s) for this key found on Target table.
- Category:
- DATA
- Cause:
- Duplicate records found at Target table.
- Action:
- Remove Duplicate records from target table OR provide an unique column for the table and then map the unique column as Primary Key in Veridata.
- OGGV-70014
- *** Insertion of data into Veridata repository started ****
- Category:
- Other
- Cause:
- Action:
- OGGV-70015
- **** Successfully Inserted data into Veridata Repository ****
- Category:
- Other
- Cause:
- Action:
- OGGV-70021
- Error in creating Veridata user {0}
- Category:
- CONFIGURATION
- Cause:
- Check the log file for cause of failure
- Action:
- Check the error messages in log file. Correct the problem before running the UA again. Contact Oracle Support Services if you are unable to correct the problem.
- OGGV-70022
- Unsupported database type {0}
- Category:
- CONFIGURATION
- Cause:
- Unsupported database type.
- Action:
- Please check the support document for valid database type.
- OGGV-70023
- Error in Veridata schema user creation
- Category:
- CONFIGURATION
- Cause:
- Check the log file for cause of failure
- Action:
- Check the error messages in log file. Correct the problem before running the UA again. Contact Oracle Support Services if you are unable to correct the problem.
- OGGV-70024
- Error in inserting data into repository
- Category:
- CONFIGURATION
- Cause:
- Error in inserting data into repository
- Action:
- Please retry. If the issue persist contact Oracle Support.
- OGGV-70025
- Error in dropping Veridata repository
- Category:
- CONFIGURATION
- Cause:
- Error in dropping Veridata repository
- Action:
- Please retry. If the issue persist contact Oracle Support.
- OGGV-70028
- Error in closing open input stream
- Category:
- CONFIGURATION
- Cause:
- Error in closing open input stream
- Action:
- Please retry. If the issue persist contact Oracle Support.
- OGGV-70206
- String ''{0}'' should match pattern ''{1}''
- Category:
- CONFIGURATION
- Cause:
- Properties pattern are mismatched.
- Action:
- Please enter the matched pattern string.
- OGGV-70208
- Error processing Veridata configuration file : {0}
- Category:
- CONFIGURATION
- Cause:
- Error processing Veridata configuration file
- Action:
- Please check the sample configuration file by refereing the veridata manual documents.
- OGGV-70211
- configureVeridata.(sh/cmd) [-pU<veridata.config.property>=<New Value>] [-redeploy -wluser=<weblogic domain admin username>] [-refreshConfig]
- Category:
- Other
- Cause:
- Action:
- OGGV-70212
- When -redeploy option is specified , Weblogic Domain Administrator user name must be specified in -wluser argument.
- Category:
- CONFIGURATION
- Cause:
- When -redeploy option is specified , Weblogic Domain Administrator user name must be specified in -wluser argument.
- Action:
- Please enter the -wluser argument option.
- OGGV-70213
- Enter the password for WebLogic Domain Administrator user {0} :
- Category:
- Other
- Cause:
- Action:
- OGGV-70214
- Property VERIDATA_ORACLE_HOME not set.
- Category:
- CONFIGURATION
- Cause:
- Property VERIDATA_ORACLE_HOME not set.
- Action:
- Please set the VERIDATA_ORACLE_HOME and refer the veridata manual for further information.
- OGGV-70216
- Failed to refresh the veridata.cfg file. File was not updated.
- Category:
- Other
- Cause:
- Action:
- OGGV-70301
- {0}
- Category:
- CONFIGURATION
- Cause:
- Technical Error
- Action:
- Check the error messages in log file. Correct the problem before running the UA again. Contact Oracle Support Services if you are unable to correct the problem.
- OGGV-70302
- Could not create user {0}.
- Category:
- CONFIGURATION
- Cause:
- Could not create the user
- Action:
- Check the error messages in log file. Correct the problem before running the UA again. Contact Oracle Support Services if you are unable to correct the problem.
- OGGV-70303
- Could not create database {0}.
- Category:
- CONFIGURATION
- Cause:
- Could not create database
- Action:
- Check the error messages in log file. Correct the problem before running the UA again. Contact Oracle Support Services if you are unable to correct the problem.
- OGGV-70304
- Could not install database {0}.
- Category:
- DEPLOYMENT
- Cause:
- Could not install database
- Action:
- Check the error messages in log file. Correct the problem before running the UA again. Contact Oracle Support Services if you are unable to correct the problem.
- OGGV-70305
- Could not drop database {0}.
- Category:
- CONFIGURATION
- Cause:
- Could not drop database
- Action:
- Check the error messages in log file. Correct the problem before running the UA again. Contact Oracle Support Services if you are unable to correct the problem.
- OGGV-70306
- Could not remove Veridata from database {0}.
- Category:
- CONFIGURATION
- Cause:
- Could not remove Veridata from database
- Action:
- Check the error messages in log file. Correct the problem before running the UA again. Contact Oracle Support Services if you are unable to correct the problem.
- OGGV-70307
- Could not drop user {0}.
- Category:
- CONFIGURATION
- Cause:
- Could not drop user
- Action:
- Please check the user permission and retry.
- OGGV-70308
- Upgrade cannot be done on {0}.
- Category:
- DEPLOYMENT
- Cause:
- Upgrade cannot be done
- Action:
- Check the error messages in log file. Correct the problem before running the UA again. Contact Oracle Support Services if you are unable to correct the problem.
- OGGV-70309
- Could not upgrade database {0}.
- Category:
- DEPLOYMENT
- Cause:
- Check the log file for cause of failure
- Action:
- Check the error messages in log file. Correct the problem before running the UA again. Contact Oracle Support Services if you are unable to correct the problem.
- OGGV-70310
- Failed to retrieve current schema version {0}.
- Category:
- CONFIGURATION
- Cause:
- Check the log file for cause of failure
- Action:
- Check the error messages in log file. Correct the problem before running the UA again. Contact Oracle Support Services if you are unable to correct the problem.
- OGGV-70311
- Failed to alter schema for tables {0}
- Category:
- CONFIGURATION
- Cause:
- Check the log file for cause of failure
- Action:
- Check the error messages in log file. Correct the problem before running the UA again. Contact Oracle Support Services if you are unable to correct the problem.
- OGGV-70312
- Failed to grant permission for user {0}
- Category:
- CONFIGURATION
- Cause:
- Check the log file for cause of failure
- Action:
- Check the error messages in log file. Correct the problem before running the UA again. Contact Oracle Support Services if you are unable to correct the problem.
- OGGV-70402
- WLS domain home argument passed to the patching script is {0}
- Category:
- Other
- Cause:
- Action:
- OGGV-70404
- Database name is either null or not specified in Veridata config file and patching cannot be continued
- Category:
- Other
- Cause:
- Action:
- OGGV-70406
- Failed to apply repository patch
- Category:
- DEPLOYMENT
- Cause:
- Failed to apply repository patch
- Action:
- Please retry. If the issue persist contact Oracle Support.
- OGGV-70409
- You are about to patch the repository and database details are - Database URL :: {0} Database User :: {1} Make sure database backup have taken up before proceeding next steps.
- Category:
- Other
- Cause:
- Action:
- OGGV-70415
- Veridata repository patching is failed.
- Category:
- DEPLOYMENT
- Cause:
- Veridata repository patching is failed.
- Action:
- Please retry. If the issue persist contact Oracle Support.
- OGGV-70416
- Expected argument is missing, Failed to apply repository patch
- Category:
- CONFIGURATION
- Cause:
- Expected argument is missing, Failed to apply repository patch
- Action:
- Please check the expected argument and enter with the help of veridata manual document.
- OGGV-80001
- Get credential for {0}.{1} failed: {2}
- Category:
- OTHER
- Cause:
- Unable to get wallet credentials. It can occur if the credentials are expired or wallet is corrupted or when proper permissions are not set for the wallet.
- Action:
- Rebuild the wallet if corrupted or reset the password if expired. Set the proper permissions and retry.
- OGGV-80002
- Put credential for {0}.{1} failed: {2}
- Category:
- OTHER
- Cause:
- Unable to Store credentials. It can happen if the credentials already exists or when the wallet is corrupted or does not have proper permissions set.
- Action:
- Create different credentials if it already exists. Rebuild the wallet if corrupted. Set the proper permissions and retry.
- OGGV-80004
- Remove credential for {0}.{1} failed: {2}
- Category:
- OTHER
- Cause:
- Unable to remove credentials. It can happen when the wallet is corrupted or does not have proper permissions set.
- Action:
- Rebuild the wallet if corrupted. Set the proper permissions and retry.
- OGGV-80005
- Update credential for WEB.{0} failed: {1}
- Category:
- OTHER
- Cause:
- Unable to update credentials. It can happen when the wallet is corrupted or does not have proper permissions set or the the credentials trying to update does not exists..
- Action:
- Rebuild the wallet if corrupted. Set the proper permissions and retry.
- OGGV-80008
- Could not get JpsContextFactory
- Category:
- DEPLOYMENT
- Cause:
- Unable to read JPS Context.
- Action:
- Check if jps-config-jse.xml exists and has the proper permissions set.
- OGGV-80010
- Could not get CredentialStore instance
- Category:
- OTHER
- Cause:
- Unable to read JPS Context. It can happen if jps-config-jse.xml does not exists or the proper permissions aren't set or if the wallet is corrupted.
- Action:
- Check if jps-config-jse.xml exists and has the proper permissions set. Rebuild the wallet if corrupted.
- OGGV-80011
- Could not check if credential exists in wallet
- Category:
- OTHER
- Cause:
- Unable to read wallet. It can happen if the wallet is corrupted or does not have the proper permissions set.
- Action:
- Set the proper permissions. Rebuild the wallet if corrupted.
- OGGV-80012
- Could not remove all credentials in map: {0}
- Category:
- OTHER
- Cause:
- Unable to delete credentials from wallet. It can happen if the wallet is corrupted or does not have the proper permissions set.
- Action:
- Set the proper permissions. Rebuild the wallet if corrupted.
- OGGV-80013
- Could not get repository password.
- Category:
- OTHER
- Cause:
- Unable to get credentials from wallet. It can happen if the wallet is corrupted or does not have the proper permissions set.
- Action:
- Set the proper permissions. Rebuild the wallet if corrupted.
- OGGV-80019
- The property {0} has not been set.
- Category:
- CONFIGURATION
- Cause:
- 'oracle.security.jps.config' property is not set.
- Action:
- Set the 'oracle.security.jps.config' property and retry.
- OGGV-80020
- Wallet ''{0}'' does not exist.
- Category:
- OTHER
- Cause:
- Wallet is not set/corrupted or does not have valid permissions.
- Action:
- Set the proper permissions / Rebuild the wallet.
- OGGV-80025
- Agent Wallet not initialized.
- Category:
- OTHER
- Cause:
- Agent Wallet is not set/corrupted or does not have the valid permissions.
- Action:
- Set the proper permissions / Rebuild the wallet.
- OGGV-80026
- Password can not be empty for key : {0}
- Category:
- DATA
- Cause:
- Password is missing or not set.
- Action:
- Set the password and retry.
- OGGV-80027
- Invalid Agent KeyStores path configuration.
- Category:
- CONFIGURATION
- Cause:
- 'server.identitystore.path' OR 'server.truststore.path' is missing or net set in the file.
- Action:
- Set the proper values for keys 'server.identitystore.path' and 'server.truststore.path' and retry.
- OGGV-80028
- Copyright (c) 2013, 2017, Oracle and/or its affiliates. All rights reserved.
- Category:
- Other
- Cause:
- Action:
- OGGV-80031
- 1.This utility reads the configuration from agent configuration properties file.
- Category:
- Other
- Cause:
- Action:
- OGGV-80032
- The agent configuration properties file needs to be updated before executing this script.
- Category:
- Other
- Cause:
- Action:
- OGGV-80033
- 2.Enter the Entry and Unlock passwords of the configured key-stores below.
- Category:
- Other
- Cause:
- Action:
- OGGV-80034
- Server Identity Store is empty or no alias names found.
- Category:
- CONFIGURATION
- Cause:
- 'server.identitystore.path' OR 'server.truststore.path' is missing or net set in the file.
- Action:
- Set the proper values for keys 'server.identitystore.path' and 'server.truststore.path' and retry.
- OGGV-80035
- Unable to find any valid alias names in Server Identity Store.
- Category:
- CONFIGURATION
- Cause:
- Unable to find any valid alias names in Server Identity Store.
- Action:
- Set valid alias in Server Identity Store.
- OGGV-80036
- Unable to find agent configuration file : {0}
- Category:
- DEPLOYMENT
- Cause:
- Unable to find agent configuration file.
- Action:
- Check if agent configuration file exists and has proper permissions set. Check the path of the file.
- OGGV-80037
- SSL Configuration of Veridata Agent with agent id : {0} is successful.
- Category:
- Other
- Cause:
- Action:
- OGGV-80038
- Error during SSL configuration, please contact System Administrator for more information.
- Category:
- OTHER
- Cause:
- Unable to configure agent wallet.
- Action:
- Please check Oracle Support document.
- OGGV-80040
- Exception stack trace
- Category:
- OTHER
- Cause:
- Unable to configure agent wallet.
- Action:
- Please check Oracle Support document.
- OGGV-80043
- Error in creating OPSS keystore service.
- Category:
- OTHER
- Cause:
- Error in creating OPSS keystore service.
- Action:
- Please check Oracle Support document.
- OGGV-80044
- Could not get VeridataWebIdentityStore
- Category:
- OTHER
- Cause:
- Could not get VeridataWebIdentityStore from OPSS.
- Action:
- Please check Oracle Support document.
- OGGV-80045
- Could not get VeridataWebTrustStore
- Category:
- OTHER
- Cause:
- Could not get VeridataWebTrustStore from OPSS.
- Action:
- Please check Oracle Support document.
- OGGV-80046
- Could not get VeridataWebSymKeyStore
- Category:
- OTHER
- Cause:
- Could not get VeridataWebSymKeyStore from OPSS.
- Action:
- Please check Oracle Support document.
- OGGV-80050
- Error during wallet export information, please contact System Administrator for more information.
- Category:
- OTHER
- Cause:
- Unable to export wallet.
- Action:
- Please check Oracle Support document.
- OGGV-80051
- Error during wallet import information, please contact System Administrator for more information.
- Category:
- OTHER
- Cause:
- Unable to import wallet.
- Action:
- Please check Oracle Support document.
- OGGV-80056
- Could not encrypt property
- Category:
- OTHER
- Cause:
- Could not encrypt property.
- Action:
- Check proper permissions are set. If yes, then verify Oracle Support document.
- OGGV-80057
- Could not decrypt property
- Category:
- OTHER
- Cause:
- Could not decrypt property.
- Action:
- Check proper permissions are set. If yes, then verify Oracle Support document.
- OGGV-80058
- Invalid JPS configuration file location : {0}
- Category:
- CONFIGURATION
- Cause:
- Could not find agent-jps-config.xml.
- Action:
- Check if file exists in proper path and has proper permissions set.
- OGGV-80059
- Invalid Veridata Wallet Map Name
- Category:
- CONFIGURATION
- Cause:
- Invalid Veridata Wallet Map Name.
- Action:
- Check Oracle Support Documentation.
- OGGV-80060
- Invalid Veridata Wallet Store Location Name : {0}
- Category:
- CONFIGURATION
- Cause:
- Invalid Veridata Wallet Store Location Name.
- Action:
- Check if location exists and has proper permissions set.
- OGGV-80061
- Invalid Veridata Wallet Store Location : {0}
- Category:
- CONFIGURATION
- Cause:
- Invalid Veridata Wallet Store Location.
- Action:
- Check if location exists and has proper permissions set.
- OGGV-80062
- Error during initializing Veridata Wallet Store.
- Category:
- OTHER
- Cause:
- Error during initializing Veridata Wallet Store.
- Action:
- Check if file location and permissions are proper. If yes, contact Oracle support.
- OGGV-80063
- Wallet Store file does not exist : {0}
- Category:
- CONFIGURATION
- Cause:
- Wallet Store file does not exist.
- Action:
- Check if file exists and permissions are proper.
- OGGV-80064
- Error during checking if key exists in wallet.
- Category:
- OTHER
- Cause:
- Error during checking if key exists in wallet.
- Action:
- Check if wallet exists and not corrupted and permissions are proper.
- OGGV-80065
- Error during getPassword in wallet.
- Category:
- OTHER
- Cause:
- Error during getPassword in wallet.
- Action:
- Check if wallet exists and not corrupted and permissions are proper.
- OGGV-80066
- Error during Wallet Store Save Operation.
- Category:
- OTHER
- Cause:
- Error during Wallet Store Save Operation.
- Action:
- Check if wallet exists and not corrupted and permissions are proper. Check for the available disk space.
- OGGV-80067
- Connection list is empty or null. No password will be exported.
- Category:
- CONFIGURATION
- Cause:
- Connection list is empty or null. No password will be exported.
- Action:
- Provide connection details and retry.
- OGGV-80068
- Failed to delete Credential Store.
- Category:
- OTHER
- Cause:
- Failed to delete Credential Store.
- Action:
- Check if wallet has proper permissions set and the files are not locked.
- OGGV-80069
- Failed to create alias ''{0}'' for user ''{1}''.
- Category:
- OTHER
- Cause:
- Failed to create alias in Wallet.
- Action:
- Check if wallet has proper permissions set and not corrupted. If corrupted then rebuild the wallet.
- OGGV-80070
- Failed to update alias ''{0}'' for user ''{1}''.
- Category:
- OTHER
- Cause:
- Failed to update alias in Wallet. It can happen if alias does not exists or the wallet is not readable or corrupted.
- Action:
- Check if alias exists and the wallet is not corrupted and has proper permissions set. If corrupted then rebuild the wallet.
- OGGV-80071
- Failed to delete alias ''{0}'' for user.
- Category:
- OTHER
- Cause:
- Failed to delete alias in Wallet. It can happen if alias does not exists or the wallet is not readable or corrupted.
- Action:
- Check if alias exists and the wallet is not corrupted and has proper permissions set. If corrupted then rebuild the wallet.
- OGGV-80072
- Failed to display alias.
- Category:
- OTHER
- Cause:
- Failed to display alias from Wallet. It can happen if alias does not exists or the wallet is not readable or corrupted.
- Action:
- Check if alias exists and the wallet is not corrupted and has proper permissions set. If corrupted then rebuild the wallet.
- OGGV-80073
- Failed to get user for alias ''{0}''.
- Category:
- OTHER
- Cause:
- Failed to get user for alias. It can happen if alias does not exists or the wallet is not readable or corrupted.
- Action:
- Check if alias exists and the wallet is not corrupted and has proper permissions set. If corrupted then rebuild the wallet.
- OGGV-80074
- Failed to get password for alias ''{0}''.
- Category:
- OTHER
- Cause:
- Failed to get password for alias. It can happen if alias does not exists or the wallet is not readable or corrupted.
- Action:
- Check if alias exists and the wallet is not corrupted and has proper permissions set. If corrupted then rebuild the wallet.
- OGGV-80075
- Alias ''{0}'' already exist in wallet.
- Category:
- DATA
- Cause:
- Unable to store alias as it already exists..
- Action:
- Provide different alias and retry.
- OGGV-80076
- Alias ''{0}'' does not exist in wallet.
- Category:
- DATA
- Cause:
- Alias does not exists in wallet.
- Action:
- Provide valid alias and check file permissions and also check if wallet is not corrupted.
- OGGV-80077
- Credential store already exist at provided location.
- Category:
- CONFIGURATION
- Cause:
- Credential store already exist at provided location.
- Action:
- Provide different wallet location.
- OGGV-80078
- Failed to create new wallet.
- Category:
- CONFIGURATION
- Cause:
- Failed to create new wallet.
- Action:
- Check the disk space and proper permissions
- OGGV-80079
- Failed to create credential store folder.
- Category:
- OTHER
- Cause:
- Failed to create credential store folder.
- Action:
- Check the credential store directory location and see if proper permissions exists for that directory. Check the disk space.
- OGGV-80080
- Jps config file already exist. Provide a new empty directory.
- Category:
- CONFIGURATION
- Cause:
- Jps config file 'jps-config-jse.xml' already exist.
- Action:
- Provide a new empty directory.
- OGGV-80081
- Failed to copy jps config file to credential store folder. Credential Store creation failed.
- Category:
- OTHER
- Cause:
- Failed to copy jps config file to credential store folder. Credential Store creation failed.
- Action:
- Check the disk space, file permissions.
- OGGV-80082
- File ''{0}'' does not exist or is not a file.
- Category:
- CONFIGURATION
- Cause:
- Jps config file 'jps-config-jse.xml' does not exist.
- Action:
- Check if JPS files exists and the file and directory has proper permissions set.
- OGGV-80083
- Failed to initialize credential store wallet.
- Category:
- OTHER
- Cause:
- Failed to initialize credential store wallet.
- Action:
- Check directory and file permissions. Check Disk space.
- OGGV-80084
- Credential store does not exist.
- Category:
- OTHER
- Cause:
- Credential store does not exist.
- Action:
- Check is wallet exists and is not corrupted or proper permissions set.