Splitting source schema into separate target schemas

[jkuzmins]

I have a source with one schema, and would like to split the tables into two separate schemas. The two schemas are still in the same target, and have been created ahead of time with the schema conversion tool. One of the schemas is the same name as the original, the other is a different name. I can load the tables that go on the schema with the original name, but when I try to load the ones to the new schema, attunity fails. Is there anything special that needs to be done to get the newly created schema to be visible to attunity?

[lyka]

Hello,

What is the source and target? Can you try by adding a global transformation and use the "Rename schema" rule.

Rename schema to (string)

Use the Rename schema to: [string] option to change the name of all table schemas that you defined in the Transformation scope step to a different name. For example, if you have a schema called Human_Resources and want to change all instances of this name to HR then enter the string HR. You can enter any string in this field.

Thanks

Lyka

[IanM]

Sounds like an auths issue. Does the Replicate user have rights to create a table in the new schema?

[john_wang]

Hello @jkuzmins , @IanM ,

In general that depends on the user/account you used in the Replicate Endpoint Definition: if the user has right to create a table or schema then Replicate will create them. This is done by standard CREATE object SQLs. If the schema exists already then Replicate can use it without re-create it again, certainly that may require some read/write privileges.

If you need additional assistance,  please set TARGET_LOAD/TARGET_APPLY to Verbose (see logging level ) and attach Diagnostics Package , we'd love to help.

Regards,

John.