Comments
Sort by recent activity
@mbruegel, From the internal ticket they have created, they have reproduced the behavior and working on a fix. No eta, though. / comments
@mbruegel, From the internal ticket they have created, they have reproduced the behavior and working on a fix. No eta, though.
For reference, ticket created (128106). / comments
For reference, ticket created (128106).
@Eddie D You guys had a change to look at this issue? / comments
@Eddie D You guys had a change to look at this issue?
@Eddie D Any input? / comments
@Eddie D Any input?
For reference, ticket created (125727). However we came to conclusion that this behavior is due to our current Oracle version has been upgraded from v9. Src and target db will be aligned upon the first deployment with SCO. / comments
For reference, ticket created (125727). However we came to conclusion that this behavior is due to our current Oracle version has been upgraded from v9. Src and target db will be aligned upon the f...
I'll try with the newest version and attached the log file. / comments
I'll try with the newest version and attached the log file.
I've tried out the new pre-filter options and it works as expected. We will do migration scripts for the other objects types. / comments
I've tried out the new pre-filter options and it works as expected. We will do migration scripts for the other objects types.
For reference, a ticket was created (125725). However resolved with a user with the correct permissions. / comments
For reference, a ticket was created (125725). However resolved with a user with the correct permissions.
For reference, ticket created (125725), but resolved by using a deployment user with correct permissions. / comments
For reference, ticket created (125725), but resolved by using a deployment user with correct permissions.
Makes sense - thanks / comments
Makes sense - thanks