| |
Results |
|
The specified schema name either does not exist or you do not have permission to use it
|
After copying an SBM database to a new database and trying to deploy an application to it, the deploy log contains the following types of error: ERROR -- UNEXPECTED ERROR: Error creating table <TABLE NAME >, ERROR -- UNEXPECTED ERROR: Error creating table <TABLE NAME>,
|
|
|
|
DimCM: Upgrade: DBI4502373E [Microsoft][SQL Server Native Client 11.0][SQL Server]The specified schema name "SCHEMANAME" either does not exist or you do not have permission to use it
|
basedb seq ------------------------- ------------------------------------------------ CM_TYPICAL PCMS_SEQ
|
|
|
|
Dim CM: DBC-IM002:0-[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
|
DMAPPSRV 2013/06/18 11:33:38 I P224 T232 Connecting to basedb @DIM10 DMAPPSRV 2013/06/18 11:33:39 E P224 T232 Pcms error: 0, Error: Unable to connect to database "basedb" DMAPPSRV 2013/06/18 11:33:39 E P224 T232 DBC-IM002:0-[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
|
|
|
|
Creating blank db with PPM 10.2 admin tool gives Parameter name: path1 error.
|
If you try to use the admin tool with PPM 10.2 and create a new connection but specify to create the database and tables you get an error that says "Value cannot be null" Parameter name : path1 and the db doesn't get created.
|
|
|
|
DIM CM 2009 R1: Error when creating a base database on SQL Server 2005
|
[Microsoft][SQL Native Client][SQL Server]The specified schema name "TEST2" either does not exist or you do not have permission to use it. Error detected in E:\Program Files\Serena\Dimensions 2009 R1\CM\dbms\mssql\translated\mssql_create_base_tables.sql, line 14 Called from E:\Program Files\Serena\Dimensions 2009 R1\CM\dbms\common\setup_base_database.sql, line 279
|
|
|
|
CMNDB2DD, problem parsing SCHEMA name of "SYSPROC".
|
Customer has specified a SCHEMA name of "SYSPROC". According to IBM DB2 DOC, SYSPROC is a reserved word and 'should' be enclosed by double quotes, when used in DDL. When CMNDB2DD processes the following statements to create a stored procedure, the name is incorrectly changed.
|
|
|
|
DimCM: Upgrade: ORA-28003: password verification for the specified password failed error during basedatabase upgrade
|
This error can happen if the basedatabase name is shorter than 8 characters, in this case Oracle is not allowing a short password, which by default would be same as the schema name . To fix this issue you will need to logon to SQLPlus as SYS (not SYSTEM) and temporarily disable password verifcation (it's recommended to open a separate command session for this procedure). First, verify which profile is used by the basedatabase user (query 1):
|
|
|
|
Reviews and experts are not triggered in Pulse when user generates a new changeset in Dimensions CM
|
This will happen if customer is using their own base database and this basedb is not specified in $DM_ROOT\dfs\alf_events_config.xml file. User must add a new <Database> section to the file, specify the basedb for the < Name > parameter there, and list all the ALF events that need to be triggered. Best option is to make a copy of the sample <Database> section and change the <Name> parameter to needed basedb@SID .
|
|
|
|
Dim200R2: How to make duplicate base database with different name?
|
will need to specify a new location for the item libraries to be located. You will need to repeat this process with each item type in all of your products. It is a very bad idea to use the same item library location for two base databases. You will run into major item library errors if you do. Please verify that you perform this step for each item type in every product. You will then want to move the backup you took in step 2 to the new location you specified in the adminconsole.
|
|
|
|
KM-Dim9: SQL-0436-1856(01A38B08) ORA-00957: duplicate column name
|
This is going to give you the duplicate (reserved) word Additionally, while connected to your base database e.g. sqlplus patrick/patrick you can validate this further as with the example specified below: SQL> desc global_attributes
|
|
|
