Oracle Error 7217 Encountered
SQL TuningSecurityOracle UNIXOracle LinuxMonitoringRemote supportRemote plansRemote servicesApplication Server ApplicationsOracle FormsOracle PortalApp UpgradesSQL ServerOracle ConceptsSoftware SupportRemote Support Development Implementation Consulting StaffConsulting PricesHelp Wanted! Oracle PostersOracle Books Oracle Scripts Ion Excel-DB Don Burleson Blog
EXP-00056: ORACLE error 942 encountered with db_link Question: I tried to export the table from client database 8.1.7 using DBLINK from our database 10.1.0.3 and got this error "EXP-00056: ORACLE error 942 encountered". Please help out. Export: Release 10.1.0.3.0 - Production on Wed Oct 12 10:27:38 2005 Copyright © 1982, 2004, Oracle. All rights reserved. Connected to: Oracle8i Enterprise Edition Release 8.1.7.0.0 - 64bit Production Enter array fetch buffer size: 4096 > Export file: expdat.dmp > test.dmp (2)U(sers), or (3)T(ables): (2)U > 3 Export table data (yes/no): yes > Compress extents (yes/no): yes > EXP-00056: ORACLE error 942 encountered ORA-00942: table or view does not exist EXP-00000: Export terminated unsuccessfully Answer by Edward Stoever: I have always used exp as a single command, not interactively. It is claiming the table does not exist, but I don't see it asking for a table - yet. (weird) Why not try it as a single command.... like this: exp scott/tiger file=emp.dmp tables=(emp,dept) I think that you are breaking the second rule there, and you should be exporting using an 8.1.7 client. The Oracle documentation notes: Whenever you are moving data between different releases of the Oracle database, the following basic rules apply: * The Import utility and the database to which data is being imported (the target database) must be the same version. * The version of the Export utility must be equal to the earliest version of the source or target database.For example, to create an export file for an import into a later release database, use a version of the Export utility that is equal to the source database. Conversely, to create an export file for an import into an earlier release database, use a version of tScript works fine if run from command-line, but if scheduled in crontab, I get errors below: ----Error log---- EXP-00056: ORACLE error 7217 encountered ORA-07217: sltln: environment variable cannot be evaluated. Username: EXP-00030: Unexpected End-Of-File encountered while reading input EXP-00000: Export terminated unsuccessfully ------End of log ----------- -----The script, http://www.dba-oracle.com/t_exp_00056_ora_942_export_database_db_link.htm $ cat export.sh--------------- TIMESTAMP=`date +%d%m%Y` export TIMESTAMP ORACLE_HOME=/ops/oracle/ora92 export ORACLE_HOME /ops/oracle/ora92/bin/exp parfile=/export/scripts/export.ctl ----------End of script------------- --------The export control file, $ cat export.ctl ------------- USERID=user/****** FILE=/export/backups/tabs_${TIMESTAMP}.dmp LOG=/export/backups/tabs_${TIMESTAMP}.log BUFFER=10000 COMPRESS=N OWNER=use_cds CONSISTENT=Y DIRECT=Y -------End of control file ----------------------------- Clearly, the problem is with some http://unix.derkeiler.com/Mailing-Lists/SunManagers/2006-04/msg00208.html environmental variable, but I can't figure out which is it. Below is the environment of the oracle user. -------Oracle Environmental variables, $ env --- _=/bin/env HZ=100 LC_MONETARY=en_US.ISO8859-1 LC_TIME=en_US.ISO8859-1 PATH=/bin:/usr/bin:/usr/openwin/bin:/usr/sbin:/usr/ccs/bin:/sbin:/ops/oracle /ora92/bin::/usr/local/bin:/ops/oracle/admin/bin:. NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1 ORACLE_BASE=/ops/oracle NOMSGLABEL=1 EDITOR=vi LOGNAME=oracle MAIL=/var/mail/oracle LOCAL_HOME=/usr/local ORACLE_SID=CDS ADMIN_HOME=/ops/oracle/admin LC_MESSAGES=C MSGVERB=text:action LC_CTYPE=en_US.ISO8859-1 SHELL=/bin/sh ORA_NLS33=/ops/oracle/ora92/ocommon/nls/admin/data HOME=/ops/oracle LC_COLLATE=en_US.ISO8859-1 LC_NUMERIC=en_US.ISO8859-1 TERM=xterm ORACLE_HOME=/ops/oracle/ora92 PWD=/export/scripts TZ=Africa/Kampala NOMSGSEVERITY=1 ------------------------------------------ Does anybody out there see the probm with cron ? Cheers, Calvin Simon Waibale. _______________________________________________ sunmanagers mailing list sunmanagers@xxxxxxxxxxxxxxx http://www.sunmanagers.org/mailman/listinfo/sunmanagers Prev by Date: Solaris machine to act as mail relay server Next by Date: Sun Cluster Logs Previous by thread: Solaris machine to act as mail relay server Next by thread: Sun Cluster Logs Index(es): Date Thread Flag as inappropriate (AWS) Security UNIX Linux Coding Usenet Mailing-ListsNewsgroupsAboutPrivacyImprint unix.derkeiler.com >Mailing-Lists >SunManagers >2006-04
variables do not work on a crone Pages 1 You must login or register to post a reply Topic http://www.progtown.com/topic557758-oraklovye-variables-do-not-work-on-a-crone.html RSS feed Posts [ 3 ] 1 Topic by A Petrov 2012-05-06 https://documentation.commvault.com/commvault/v10/article?p=products/oracle/snap/troubleshooting.htm 05:06:37 A Petrov Member Offline Registered: 2012-05-03 Posts: 121 Topic: Oraklovye variables do not work on a crone I launch an aaplet on Perl:#!/usr/bin/perl-w` NLS_DATE_FORMAT = "DD/MM/YYYY hh:mi:ss" `;` NLS_LANG = "AMERICAN_AMERICA.RU8PC866" `;` ORACLE_BACE =/dir `;` ORACLE_HOME =/dir/dir2 `;` ORACLE_SID=sid `;` export NLS_DATE_FORMAT NLS_LANG ORACLE_BACE oracle error ORACLE_HOMEORACLE_SID `;$exec: = "/dir/dir2/bin/imp user/passwd full=y ignore=y file =/dir3/filename1";` $exec `;Manually works super, and on a crone -IMP-00058: ORACLE error 7217 encounteredORA-07217: sltln: environment variable cannot be evaluated. Username:IMP:00000: Import terminate unsuccessfullyWhy does not work on a crone? 2 Reply by Vyacheslav Ljubomudrov 2012-05-06 05:29:37 Vyacheslav Ljubomudrov Member Offline Registered: 2012-05-02 Posts: 15,713 Re: Oraklovye variables oracle error 7217 do not work on a crone . wrote: I Launch an aaplet on Perl:#!/usr/bin/perl-w` NLS_DATE_FORMAT = "DD/MM/YYYY hh:mi:ss" `;` NLS_LANG = "AMERICAN_AMERICA.RU8PC866" `;` ORACLE_BA A C E =/dir `;` ORACLE_HOME =/dir/dir2 `;` ORACLE_SID=sid `;` export NLS_DATE_FORMAT NLS_LANG ORACLE_BA A C E ORACLE _ HOMEORACLE _SID `;$exec: = "/dir/dir2/bin/imp user/passwd full=y ignore=y file =/dir3/filename1";` $exec `;Manually works super, and on a crone -IMP-00058: ORACLE error 7217 encounteredORA-07217: sltln: environment variable cannot be evaluated. Username:IMP:00000: Import terminate unsuccessfullyWhy does not work on a crone? And in the manual works, because these variables at you are installed, for example, in a profile. And the profile does not fulfill crones 3 Reply by Vladimir Begun 2012-05-06 05:49:38 Vladimir Begun Member Offline Registered: 2012-05-02 Posts: 1,549 Re: Oraklovye variables do not work on a crone . wrote:... [code] $ENV {' ORACLE_HOME '} = '/oh ';$ENV {' ORACLE_SID '} = ' sid ';... Posts [ 3 ] Pages 1 You must login or register to post a reply Programmer's Town »Databases »Oraklovye variables do
in Indexing Operation (Create or Update Index) Make sure to perform a crosscheck archive log all operation. Then, retry the IntelliSnap backup operation. Failed during VSS IntelliSnap Backup Verify the Windows Event Viewer, if any error occurs during the VSS IntelliSnap backup operation.There is a known issue with Oracle VSS Writer memory leak (metalink ID 1358570.1). Hence, if Oravssw.exe consumes more memory, restart the service. IntelliSnap Backup Fails IntelliSnap Backup operations fail if the database is in the NOARCHIVELOG mode. Alter the database to ARCHIVELOG mode and then perform the IntelliSnap backups. SQL>startup mount; SQL>alter database archivelog; SQL>alter database open; Sometimes, the IntelliSnap backup operations may fail if you enable the SSKIPBACKUPBROWSE Additional Setting. Disable it. Mount Operation Fails on Windows During RMAN backup copy operation on proxy, the mount operations fails with the following error message: OS mount failed : [Mount failed: E_FAIL (MM.60611)] To resolve this issue make sure the mount directory is empty and there are no drives (same as source data drives) exist on the proxy. IntelliSnap restores of high transaction rate databases may fail Do not use IntelliSnap to back up archive log volume of high transaction databases, because the following errors may be encountered while restoring from those snaps or during the backup copy of those IntelliSnap jobs. ORA-00283: recovery session canceled due to errors ORA-00354: corrupt redo log block header ORA-00353: log corruption near block 86016 change 7963079914 time 01/28/2014 09:54:46 Instead back up the archive logs using RMAN. Select the Use Rman for Log Backup check box on the Logs Backup tab of the Subclient Properties dialog box. IntelliSnap backup job runs indefinitely IntelliSnap Backup operations may run indefinitely due to following reasons: If the archive log location is ful