ORA-29283: invalid file operation

Error: ORA-29283: invalid file operation

Details: Error occurs when running a full data pump export

Cause:DATA_PUMP_DIR is not defined or defined incorrectly for that database Solution:Login to sqlplus as sysdba and execute:

CREATE OR REPLACE DIRECTORY DATA_PUMP_DIR as 'your dir path here';

SSIS Error : Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state."

Error:Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.

Details: Error occurs after deploying SSIS package to another server

Cause:Incorrect package protection level specified - by default it is EncryptSensitiveWithUserKey
Solution:Change package protection level property to to EncryptSensitiveWithPassword, or EncryptAllWithPassword and provide the password

SSIS Error Code DTS_E_OLEDB_NOPROVIDER_64BIT_ERROR

Error: SSIS Error Code DTS_E_OLEDB_NOPROVIDER_64BIT_ERROR. The requested OLE DB provider OraOLEDB.Oracle.1 is not registered -- perhaps no 64-bit provider is available.

Details: Error occurs when attempting to run a SQL Agent job that runs SSIS package that opies data from Oracle to SQL Server

Cause:64 bit OLE DB provider Microsoft.Jet.OLEDB.4.0 is not installed on a 64-bit machine.
Solution:Run the SQL Agent job in 32 bit mode:

1. Right-click on the job name and select Properties
2. Go to Steps
3. Select the step your job fails on and click Edit
4. Select "execution optons" tab and check a "use 32 bit runtime" checkbox

[OLE DB Source [45]]: Cannot retrieve the column code page info from the OLE DB provider

Error: [OLE DB Source [45]]: Cannot retrieve the column code page info from the OLE DB provider. If the component supports the "DefaultCodePage" property, the code page from that property will be used. Change the value of the property if the current string code page values are incorrect. If the component does not support the property, the code page from the component's locale ID will be used.

Details: This error occurs attempting to view colmuns of an OleDB data source in a Data Flow task inside the Business Intelligence Development Studio, while attempting to do a data transfer between Oracle and SQL Server databases


Cause:It is actually only a warning that means that the data provider does not publish code pages used for text columns and also that SSIS does not do implicit conversions between Unicode and non-unicode strings

Solution:We can get rid of this warning by setting AlwaysUseDefaultCodePage property of the OLE DB Source Data Flow Component to True. It is set by default to False but can be changed easily from the Properties window in Business Intelligence Development Studio project.

ORA-31634: job already exists

Error: ORA-31634: job already exists ORA-31664: unable to construct unique job name when defaulted

Details: Error occurs when running a full data pump export

Cause:The table dba_datapump_jobs contains 99 orphaned jobs: The SQL below returns 99 rows:

select owner_name, job_name, state from dba_datapump_jobs order by job_name;

Solution:Remove the jobs that are not ruuning and purge them from recycle bin:

DROP TABLE OWNER_NAME.JOB_NAME;


PURGE DBA_RECYCLEBIN;


or


DROP TABLE OWNER_NAME.JOB_NAME PURGE;

ORA-19705: tag value exceeds maximum length of 31 characters

Error: ORA-19705: tag value exceeds maximum length of 31 characters

Details: This error occurs when running a backup

Cause:The database either crashed or was shutdown with the ABORT option. Media recovery cannot be enabled because the online logs may not be sufficient to recover the current datafiles.

Solution:Supply a shorter tag in the backup script and retry the operation.

ORA-00265: instance recovery required, cannot set ARCHIVELOG mode

Error: ORA-00265: instance recovery required, cannot set ARCHIVELOG mode

Details: This error occurs when switch databas eto ARCHIVELOG mode by executing:
ALTER DATABASE ARCHIVELOG;

Cause:The database either crashed or was shutdown with the ABORT option. Media recovery cannot be enabled because the online logs may not be sufficient to recover the current datafiles.

Solution:Open the database and then enter the SHUTDOWN command with the NORMAL or IMMEDIATE option:

>ALTER DATABASE OPEN;

>SHUTDOWN IMMEDIATE;