problem in oa2cdb conversion

R

RC MURALI

Guest
Hi,

I was trying to convert a library in OA database to CDB through
command line, using the following command.

oa2cdb -lib TEST_LIB -cdslibpath /home/username/cds.lib -cdblibpath /
home/username/CDBLIB/ -tech /home/username/TECHLIB/tsmcN45

In the cds.lib file, the library TEST_LIB is defined.

The folder CDBLIB is newly & already created.

It gives the following errors after execution of the above command:



*WARNING* envGetVal: Could not find variable 'dbStatCacheOn'
in tool[.partition] 'cdba'.
*WARNING* envGetVal: Could not find variable 'dbInstNamingGlobalInc'
in tool[.partition] 'cdba'.
ERROR (OACDB-136): The -cdblibpath option cannot be used because the
CDB
version of library "TEST_LIB" already exists.
Type "oa2cdb -h" for help on syntax and usage.

INFO (OACDB-820): oa2cdb translation failed.


How to get rid of this error?

Thanks & Regards,
Murali RC
 
RC MURALI wrote, on 01/21/10 04:57:
Hi,

I was trying to convert a library in OA database to CDB through
command line, using the following command.

oa2cdb -lib TEST_LIB -cdslibpath /home/username/cds.lib -cdblibpath /
home/username/CDBLIB/ -tech /home/username/TECHLIB/tsmcN45

In the cds.lib file, the library TEST_LIB is defined.

The folder CDBLIB is newly& already created.

It gives the following errors after execution of the above command:



*WARNING* envGetVal: Could not find variable 'dbStatCacheOn'
in tool[.partition] 'cdba'.
*WARNING* envGetVal: Could not find variable 'dbInstNamingGlobalInc'
in tool[.partition] 'cdba'.
ERROR (OACDB-136): The -cdblibpath option cannot be used because the
CDB
version of library "TEST_LIB" already exists.
Type "oa2cdb -h" for help on syntax and usage.

INFO (OACDB-820): oa2cdb translation failed.


How to get rid of this error?

Thanks& Regards,
Murali RC
oa2cdb -h says:

-cdblibpath <t_cdbLibPath>
Specifies the directory for the CDB version of the
library. The last element of the path is the library
directory, into which the library cells and other
files are to be translated.

Note: The cds.lib file is always updated or created
in the current directory. If you do not specify
-cdblibpath, the library is translated into the
current directory. This option only makes sense when
the CDB library does not already exist.

I expect you're running in /home/username - and so it is trying to update the
cds.lib in that directory to add the entry for the newly created CDB version of
TEST_LIB, but of course the cds.lib in that directory is pointing to the OA version.

So run the command in a directory where you want to create the new cds.lib -
maybe in the /home/username/CDBLIB directory.

The two envGetVal warnings are well known - there's a CCR for this - but they've
not been fixed. To be honest, oa2cdb is intended as an emergency route back to
IC5141, and should not be used as part of a production flow, so the odd warning
shouldn't be an issue.

Regards,

Andrew.
 
On Jan 21, 3:11 pm, Andrew Beckett <andr...@DcEaLdEeTnEcTe.HcIoSm>
wrote:
RC MURALI wrote, on 01/21/10 04:57:



Hi,

I was trying to convert a library in OA database to CDB through
command line, using the following command.

oa2cdb -lib TEST_LIB -cdslibpath /home/username/cds.lib -cdblibpath /
home/username/CDBLIB/ -tech /home/username/TECHLIB/tsmcN45

In the cds.lib file, the library TEST_LIB is defined.

The folder CDBLIB is newly&  already created.

It gives the following errors after execution of the above command:

*WARNING* envGetVal: Could not find variable 'dbStatCacheOn'
         in tool[.partition] 'cdba'.
*WARNING* envGetVal: Could not find variable 'dbInstNamingGlobalInc'
         in tool[.partition] 'cdba'.
ERROR   (OACDB-136): The -cdblibpath option cannot be used because the
CDB
                      version of library "TEST_LIB" already exists.
                      Type "oa2cdb -h" for help on syntax and usage.

INFO    (OACDB-820): oa2cdb translation failed.

How to get rid of this error?

Thanks&  Regards,
Murali RC

oa2cdb -h says:

-cdblibpath <t_cdbLibPath
                   Specifies the directory for the CDB version of the
                   library. The last element of the path is the library
                   directory, into which the library cells and other
                   files are to be translated.

                   Note: The cds.lib file is always updated or created
                   in the current directory. If you do not specify
                   -cdblibpath, the library is translated into the
                   current directory. This option only makes sense when
                   the CDB library does not already exist.

I expect you're running in /home/username - and so it is trying to update the
cds.lib in that directory to add the entry for the newly created CDB version of
TEST_LIB, but of course the cds.lib in that directory is pointing to the OA version.

So run the command in a directory where you want to create the new cds.lib -
maybe in the /home/username/CDBLIB directory.

The two envGetVal warnings are well known - there's a CCR for this - but they've
not been fixed. To be honest, oa2cdb is intended as an emergency route back to
IC5141, and should not be used as part of a production flow, so the odd warning
shouldn't be an issue.

Regards,

Andrew.
Hi,

Inside the /home/username/CDBLIB/ directory, I created a cds.lib file
and defined the cdb tech file.

There is nothing in the CDBLIB directory, other than this cds.lib file

Then I ran the following command from here,

oa2cdb -lib TEST_LIB -cdslibpath /home/username/cds.lib


It gave the following error.

" Segmentation fault (core dumped)"

It has created a core file in the directory.

How to get rid of this error?

Thanks & Regards,
Murali RC
 
RC MURALI wrote, on 02/02/10 14:59:
On Jan 21, 3:11 pm, Andrew Beckett<andr...@DcEaLdEeTnEcTe.HcIoSm
wrote:
RC MURALI wrote, on 01/21/10 04:57:



Hi,

I was trying to convert a library in OA database to CDB through
command line, using the following command.

oa2cdb -lib TEST_LIB -cdslibpath /home/username/cds.lib -cdblibpath /
home/username/CDBLIB/ -tech /home/username/TECHLIB/tsmcN45

In the cds.lib file, the library TEST_LIB is defined.

The folder CDBLIB is newly& already created.

It gives the following errors after execution of the above command:

*WARNING* envGetVal: Could not find variable 'dbStatCacheOn'
in tool[.partition] 'cdba'.
*WARNING* envGetVal: Could not find variable 'dbInstNamingGlobalInc'
in tool[.partition] 'cdba'.
ERROR (OACDB-136): The -cdblibpath option cannot be used because the
CDB
version of library "TEST_LIB" already exists.
Type "oa2cdb -h" for help on syntax and usage.

INFO (OACDB-820): oa2cdb translation failed.

How to get rid of this error?

Thanks& Regards,
Murali RC

oa2cdb -h says:

-cdblibpath<t_cdbLibPath
Specifies the directory for the CDB version of the
library. The last element of the path is the library
directory, into which the library cells and other
files are to be translated.

Note: The cds.lib file is always updated or created
in the current directory. If you do not specify
-cdblibpath, the library is translated into the
current directory. This option only makes sense when
the CDB library does not already exist.

I expect you're running in /home/username - and so it is trying to update the
cds.lib in that directory to add the entry for the newly created CDB version of
TEST_LIB, but of course the cds.lib in that directory is pointing to the OA version.

So run the command in a directory where you want to create the new cds.lib -
maybe in the /home/username/CDBLIB directory.

The two envGetVal warnings are well known - there's a CCR for this - but they've
not been fixed. To be honest, oa2cdb is intended as an emergency route back to
IC5141, and should not be used as part of a production flow, so the odd warning
shouldn't be an issue.

Regards,

Andrew.

Hi,

Inside the /home/username/CDBLIB/ directory, I created a cds.lib file
and defined the cdb tech file.

There is nothing in the CDBLIB directory, other than this cds.lib file

Then I ran the following command from here,

oa2cdb -lib TEST_LIB -cdslibpath /home/username/cds.lib


It gave the following error.

" Segmentation fault (core dumped)"

It has created a core file in the directory.

How to get rid of this error?

Thanks& Regards,
Murali RC
Make sure you're using the latest hotfix of IC613, or try IC614, and if it still
happens, contact Cadence Customer Support. The problem is almost certainly data
specific, and there's really nothing that can be gleaned by a generic crash
message as above.

Regards,

Andrew.
 

Welcome to EDABoard.com

Sponsor

Back
Top