Conference orarep::nomahs::repository

1079.0. "BLRSYNERR, What is causing it?" by M5::GHODSON () Mon Apr 07 1997 16:37

This is a reference for bug # 475617


The customer is trying to integrate his Rdb database into CDD.  He is
getting errors:

cdd-e-blrsynerr   syntax error blr buffer at offset 0

He is using CDD 5.3.  He sent us a copy of his RMU/EXTRACT/ITEM=ALL and
here are the results of trying to integrate the database here.  The
RMU/Extract is located at:

        M5::DISK$USER:[GHODSON.HOLD]BLRSYNERR.SQL

It is set up without hardcoded device names and minimal initial allocation
sizes so if you do:

mcr sql$
sql>@BLRSYNERR.SQL

you will get the files:

CORS.RDB;1               163/164
CORS_IND.RDA;1           208/208
CORS_IND.SNP;1            22/24
CORS_RDA1.RDA;1          208/208
CORS_RDA1.SNP;1           22/24
CORS_SYS.RDA;1         55374/55376
CORS_SYS.SNP;1         26830/26832


Integrating with CDD 6.1
------------------------
$ rmu/show ver
Executing RMU for DEC Rdb V6.1-1
$ mcr cdo
Welcome to CDO V6.1
The CDD/Repository V6.1 User Interface
Type HELP for help
CDO>  Exit
$ mcr sql$
SQL> integrate database filename cors.rdb create pathname cors;
%CDD-E-DEFCHAR, Character set of default value and field do not match
SQL>  Exit


Integrating with CDD 6.1-03 or CDD 7.0
--------------------------------------
$ rmu/show ver
Executing RMU for Oracle Rdb V7.0-0
$ mcr cdo
CDO> show version
Installed version of Oracle CDD/Repository is V7.0
CDO> exit
$ mcr sql$70
SQL> integrate database filename cors.rdb create pathname cors;
%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 27
%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 26
%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 23
%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 41
%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 25
%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 29
%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 27
%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 29
%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 25
%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 19
%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 26
%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 25
%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 35
%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 35
%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 24
%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 30
%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 30
%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 41
%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 26
%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 28
%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 33
%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 40
%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 24
SQL> commit;
SQL> exit;

What objects in the database are causing these errors?

Hi Gary,

> This is a reference for bug # 475617

	Why did you submit a bug for this? It works in CDD/Repository V6.1-03 	
	and CDD/Repository V7.0. This is the fix you should propose to the
	customer.


> cdd-e-blrsynerr   syntax error blr buffer at offset 0

        CDD/R version 5.3 is no longer supported. Please upgrade.

>SQL> integrate database filename cors.rdb create pathname cors;
>%CDD-E-DEFCHAR, Character set of default value and field do not match
>SQL>  Exit

	This is fixed in CDD V6.1-01 .


>SQL> integrate database filename cors.rdb create pathname cors;
>%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 27
>%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 26
>%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 23
>%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 41
>%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 25
>%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 29
>%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 27
>%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 29
>%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 25
>%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 19
>%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 26
>%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 25
>%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 35
>%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 35
>%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 24
>%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 30
>%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 30
>%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 41
>%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 26
>%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 28
>%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 33
>%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 40
>%CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 24
>SQL> commit;

	These are just informationnal messages, not errors. CDD just says to
	you that some attributes are not fully supported. Those objects are
	just tolerated, marked incomplete and the INTEGRATE continues.
	In your case, you have 23 indices using Node size clause and Percent
	fill clause. These attributes generate MBLRSYNINFO informational 
	messages. Starting with CDD/Repository V6.1, you can define 
	CDD$DEBUG_FLAGS to O to see which entity is causing the error such:
   ...
   %CDD-I-MBLRSYNINFO, unsupported entity - marked Incomplete at mblr offset 27
    Integrating entity: H_JOB_CD__SSN
        type: INDEX    action: DEFINE    target: DICTIONARY
   ...


Hope this helps.

Patrick

    
    Aside of this, did you note that the pathname cannot be dropped by 
    		SQL> drop pathname cors;
    
    It gives the SQL prompt without error but the CDD$DATABASE object is
    still there under CDO. 
    
    This has to be reported.
    
    Patrick