Browsing Solutions For ArchiveManager

  • ArchiveManager (DIET) imports receive "Object X of type Y referenced on line ??? and never defined" errors

    Running an ArchiveManager (DIET) import can sometimes produce the following messages: Object '<obj_type>_123456789' of type '<obj_type>' referenced on line XXX and never defined ...where <obj_type> is the Clarify database object, such as bus_org, gbst_elm, site, etc. This message means the OBJECT or REFERENCE definition block for the <obj_type>_123456789 does not exist in the import file and that other OBJECTs and REFERENCEs refer to it. Since it cannot make this association, proper relations in the database cannot be made and the import fails.

  • How to use a where clause in a DIET directive file

    When using DIET (ArchiveManager) to export, purge, or archive data, a where clause can be used in the directive file to limit the scope of objects. The syntax can be a little tricky, especially when the clause contains spaces. Examples may be useful.

  • error: diet.exe has stopped working, diet crashes using an empty directives file

    Performing a purge or archive operation using DIET (ArchiveManager) with an empty (zero byte) directive file can cause DIET to crash. The exact error message may be varied, sepending on your specific environment and debugger settings. It could be something like: An unhandled win32 exception occured in diet.exe OR diet.exe has stopped working This was reported using DIET version 2.2.1, although the issue also exists in earlier versions.

  • Running DIET on SQL Server throws error: ntwdblib.dll not found

    DIET (as of version 2.1.11) uses SQL Server db library (ntwdblib.dll) to connect to SQL Server databases. As of SQL Server 2005, this library is no longer shipped with the database engine. Additional Information: Although the SQL Server 2005 Database Engine still supports connections from existing applications using the DB-Library and Embedded SQL APIs, it does not include the files or documentation needed to do programming work on applications that use these APIs. A future version of the SQL Server Database Engine will drop support for connections from DB-Library or Embedded SQL applications. Do not use DB-Library or Embedded SQL to develop new applications. Remove any dependencies on either DB-Library or Embedded SQL when modifying existing applications. Instead of these APIs, use the SQLClient namespace or an API such as OLE DB or ODBC. SQL Server 2005 does not include the DB-Library DLL required to run these applications. To run DB-Library or Embedded SQL applications you must have available the DB-Library DLL from SQL Server version 6.5, SQL Server 7.0, or SQL Server 2000. Keywords: SQL, Server, 2005, 2008, ntwdblib.dll

  • DIET error: ERROR - ORA-00932: inconsistent datatypes: expected %s got %s

    ArchiveManager (DIET) throws an Oracle error: ERROR - ORA-00932: inconsistent datatypes: expected %s got %s

  • DIET error: FATAL - Can not find unique field or relation

    When using DIET (ArchiveManager), the following error may be displayed: FATAL - Can not find unique field or relation 'foo' Note that the field or relation name (in this case, "foo") may be different in your environment.

  • 'Parse Error' or 'Bad argument' message for WHERE Clause in Archive Manager (DIET)

    When Archive Manager (DIET) directive file or command line contains WHERE clause to specify object selection criteria, an error messages like: ERROR - Bad argument your_argument_or_operand_or_value or: Parse error, found '=', expected "(", ",", ";", "end_routine", "end_to", "to", "to_exclusive", "if", string or quoted string may be shown to the user.

  • DIET errors when the username is not "sa" on Oracle databases

    When using DIET on Oracle databases, and the username is not SA, then errors can occur, such as: Unique field 'login_name' not specified

  • How to have DIET import multiple files at one time

    DIET (Archive Manager) can import multiple DAT files at one time. This allows for import flexibility, such as having all your common references in one file. What is the syntax for importing multiple files at one time?

  • Archiving Oracle LONG fields truncates data from fields with more than 32K in them

    When archiving data using Archive Manager (formerly known as DIET) from an Oracle database containing records with fields of type LONG having more than 32K of data you will get the following error: ERROR - ORA-01406: fetched column value was truncated Only the first 32K of data from the LONG field for the record will be written to the archive.

  • DIET would hang in input mode.

    When executing DIET against a Microsoft SQL Server or Oracle database. Execution stops after displaying this message: DIET version 2.1.12(d) for Oracle 9i for NT Copyright 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006. First Choice Software, Inc. Compiled Apr 25 2007 13:47:00 Run Time Thu Jun 19 16:42:59 2008 The user must press Ctrl+C to exit the application.

  • DIET Fatal error message: Can not export on Clarify version 12 or above on Oracle

    Performing an export with DIET in Oracle on Clarify 12 or above yields an error: DIET version 2.1.12(d) for Oracle 9i for NT Copyright 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006. First Choice Software, Inc. Compiled Apr 25 2007 13:47:00 Run Time Thu Jun 05 17:10:03 2008 NOTICE - logging into database, pulling basic object information FATAL - Can not export on Clarify version 12 or above on Oracle Compilation Unsuccessful : 1 Notices Encountered 1 Fatal Errors Encountered DIET version 2.1.12(d) for Oracle 9i for NT ...

  • DIET ERROR - ORA-01403: no data found

    When importing, exporting, or purging data using DIET ( Archive Manager ), the following Oracle error can occur: ORA-01403: no data found

  • DIET error: Checksum parameter is not the license key

    DIET can throw the following error when trying to add a checksum to a directive file: FATAL - Checksum parameter is not the license key diet –archive –directive file.arc –checksum <DietLicenseKey>

  • DIET error: Objid can not be a unique field unless -objid is used

    DIET can throw an error such as: ERROR - Objid can not be a unique field unless -objid is used

  • DIET ( ArchiveManager ) error: File 'file.arc' has a bad check sum

    DIET ( PARE DIET, ArchiveManager ) can throw the following error: ERROR - File 'zip.arc' has a bad check sum

  • Will DIET work with Oracle 8.1.7?

    Will DIET work with Oracle 8.1.7?

  • Corrupt date format in DIET archive files

    When performing a purge, archive, or export using DIET, and explicitly setting a date_format, the resulting dates in the output file can be corrupt. For example, using this diet command: diet -archive -dir acd.dir -export acd.dat -date_format "%d/%m/%Y %H:%M:%S" can result in the output file having entries such as: creation_time = DATE "m/H:S"; In the output file, the DATE_FORMAT is listed as: DATE_FORMAT "m/H:S" This happens when running DIET on Windows.