Define Veridata To Use The Existing Default Temp Tablespace

(Doc ID 2326946.1)

Last updated on JANUARY 18, 2018

Applies to:

Oracle GoldenGate Veridata - Version 12.2.1.2.0 and later
Information in this document applies to any platform.

Goal

We created the Veridata schema but at the database level, we saw that the schemas have created two temporary table spaces as below.

In our environment, all the schemas have to use just the temp tablespace so could you let us know how we can define veridata to use the existing default temp tablespace and not create its own tablespace.


TABLESPACE_NAME FILE_NAME
------------------------------ ---------------------------------------------------------------------------------------------------
TEMP +QOSSO1P_DATA/qosso1p/tempfile/temp.616.782905303
SSO_IAS_TEMP +QOSSO1P_DATA/qosso1p/tempfile/sso_ias_temp.306.956937689
SSO_VERIDATA_TEMP +QOSSO1P_DATA/qosso1p/tempfile/sso_veridata_temp.303.956935271
TEMP +QOSSO1P_DATA/qosso1p/tempfile/temp.474.784560835
I can see only the below statement. How to specify the default location?

----Default and temporary tablespaces for the repository (if you will be creating a new user for the server component during installation)

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms