10

For anyone else stuck with this, here's the solution. Oracle 12c introduces multitenancy. With this architecture the Tridion Content Delivery database must be set up in the pluggable database rather than the container database that is the default when you first connect via sqlplus. To switch to the pluggable database you will need to log in "sys as sysdba" ...


2

This is an Oracle specific error (not related to Tridion) and it occurs because of the scope/container where you are trying to create the user in the Oracle DB. You should try option mentioned in the below link which should resolve the issue: https://dba.stackexchange.com/questions/60806/oracle-12c-create-user Couple of other links describing the issue and ...


1

You can obviously encrypt database credentials that you specify in your cd_storage.conf. Since your question is based on a transporter, the first thing you would do is to check with SDL support. For your understanding, you can decompile the cd jar under the "com.tridion.transport.connection.connectors" namespace if your above sender is supported. If your ...


1

Apparently we used the wrong namespace due to the database setup not being default.


1

Tridion had a Legacy pack installed. Thus, Oracle ODAC 64-bit would not allow me to publish and (presumably) caused the error. 1. Removed Legacy pack from Tridion installation - after I installed and verified it would not work by simply installing the 32-bit ODAC Oracle client. 2. Then I removed both 32-bit & 64-bit versions of Oracle ODAC client via ...


Only top voted, non community-wiki answers of a minimum length are eligible