Error Message: "OBJECTS_OBJREF_NOT_ASSIGNED"

[Former Member]

Hi All,

One of our cube to which we are picking the data from oracle using DBConnect creating a problem. In monitor screen, the request is still running. But in ST22, it throwed a runtime error with the short text "Access not possible using 'NULL' object reference."

Following is the log we found in SM37:-

04:30:25 Job started
04:30:25 Step 001 started (program RSBATCH1, variant &000
04:30:28 Start InfoPackage ZPAK_49H0QZHXXI388W5UL17HMHOJC
04:42:15 SQL: 11.11.2008 04:42:15 SRIKANTH
04:42:15 ALTER TABLE "/BIC/FZNCUNDAT1" ADD PARTITION
04:42:15 "/BIC/FZNCUNDAT10000000351" VALUES LESS THAN
04:42:15 (0000000351 ) TABLESPACE "PSAPPBW"
04:42:15 SQL-END: 11.11.2008 04:42:15 00:00:00
04:42:16 SQL: 11.11.2008 04:42:16 SRIKANTH
04:42:16 ALTER TABLE "/BIC/FZNCUNDAT1" MODIFY PARTITION
04:42:16 "/BIC/FZNCUNDAT10000000351" REBUILD UNUSABLE
04:42:16 LOCAL INDEXES
04:42:16 SQL-END: 11.11.2008 04:42:16 00:00:00
04:42:16 SQL: 11.11.2008 04:42:16 SRIKANTH
04:42:16 ANALYZE TABLE "/BIC/FZNCUNDAT1" PARTITION (
04:42:16 "/BIC/FZNCUNDAT10000000351" ) ESTIMATE STATISTIC
04:42:16 SAMPLE 10 PERCENT
04:42:16 SQL-END: 11.11.2008 04:42:16 00:00:00
04:44:26 ABAP/4 processor: OBJECTS_OBJREF_NOT_ASSIGNED
04:44:26 Job cancelled

We are not using any routine in the update rules. We also tried to load upto psa, then also it gave the same error. We are using BW3.5.

Please help us to solve this issue.

Regards,

Yokesh.

Edited by: YOKESH KUMAR VELUSAMY on Nov 11, 2008 11:57 AM

[Former Member]

We found a workaround for the problem by reducing the number of records per packet in the Default Data Transfer setting option which is present in the info package.

After changing the settings, the data is loaded into the target successfully.

[Former Member]

Hi Reddy,

The problem got solved. Actually, it is not a table space issue since there is enough table space. We are picking the data from DBConnect. And the number of records to be picked by this request is exactly 5000. In Data S. Default Data Transfer Settings options in the Info Package, the no of records per packet had been set to 5000 (the default value). We changed this to 2500, but again we got the same error. We changed it to 3000, and the data loaded. Could this be because the number of records to be loaded (5000) was an exact multiple of the previous data transfer settings (2500 and 5000)? The moment we set it to a non-multiple, the data loaded succesffully.

The OSS note 987104 suggests this problem happens when the source SQL table doesn't contain data. But here it contains 5000 records. Anyway, it is solved for now. Thanks for your help, Reddy

Edited by: YOKESH KUMAR VELUSAMY on Nov 11, 2008 2:21 PM

[former_member181964]

Hi,

I think this is the table space problem TABLESPACE "PSAPPBW" so check with basis team.

[Former Member]

Hi Reddy,

Thanks for ur immediate response.

OSS Note: 1004691 comes into picture when we try to implement anything using t.code SNOTE. But in our case, we are just loading the data...

So, it is not relevant to this problem.

Pls helps us to overcome this issue.

Regards,

Yokesh.

[former_member181964]

Hi,

Check OSS Note: 1004691

Thanks

Reddy