Question Re: Errors occured during extraction in Technology Q&A

Errors occured during extraction

Former Member — Fri, 17 Feb 2006 16:21:09 GMT

Hello,

Recently our BW development was restored from a current backup. We didn't lose any changes as the backup was current.

After the restore I had to activate my infosources before they would work correctly for the sake of data loading. If I don't do that then I get SAPI errors during infopackage loads.

I have a particular load that is failing me. It loads data from infocube 0COPC_C09 to ODS ZCOPC_05.

When I go to RSA3, I use 80COPC_C09 as the datasource and i start extraction. I get an message that says:

"Errors occurred during the extraction."

When I display the log:

I see this -

"SQL Error: 1101"

I do not get any short dumps in ST22, unless I don't delete the previous unactivate request in the data target.

I am not loading from a flat file.

I am not using any selection values either.

Does anyone have any suggestions?

Thanks,

Nick

Re: Errors occured during extraction

Former Member — Fri, 17 Feb 2006 18:05:54 GMT

Hi Nick,

The entire message is just the SQL Error?

There are several notes regarding the 1101 error, but just "SQL Error: 1101" is too general.

If you have more details, it´d be better.

Regards,

Tomas

Re: Errors occured during extraction

Former Member — Fri, 17 Feb 2006 20:12:13 GMT

This is the generic message on the status tab in Monitor. However there is no more explanation to the SQL error

Error message from the source system

Diagnosis

An error occurred in the source system.

System response

An error occurred in Extractor .

Check the error message.

Procedure

The procedure for removing errors takes place depending on

the error message:

Note

If the source system is a Client Workstation, then it is possible that the file that was to be loaded was being edited at the time of the data request. Make sure that the file is in the specified directory and is not being edited, and restart the request.

Let me know if you would require any other information.

Thanks,

Nick

Re: Errors occured during extraction

Former Member — Sat, 18 Feb 2006 06:09:07 GMT

Hi Nick,

Just try to Replicate the DS again and run the program RS_TRANSTRU_ACTIVATE_ALL for the particular Infosource,and then try again , may be the DS Generated Program is unable to access the data .

let me know what happenend.

Thanks,

Krish

Re: Errors occured during extraction

Former Member — Mon, 20 Feb 2006 09:14:01 GMT

Hi Nick,

Is it Delta or Full load that you are trying.

Regards,

Rohini

Re: Errors occured during extraction

Former Member — Mon, 20 Feb 2006 14:19:08 GMT

Hello Krishna and Rohini,

Krishna - I can replicate the DS again. I have no idea how to run the RS_TRANSTRU_ACTIVATE_ALL for the particular Infosource. Can you help me out in that regard?

Rohini - I am attempting a full load.

Thanks,

Nick

Re: Errors occured during extraction

Former Member — Mon, 20 Feb 2006 14:23:57 GMT

Hi Nick,

You can run RS_TRANSTRU_ACTIVATE_ALL in SE38. When you click on Execiute, you will have to enter the Source System and then the name of the InfoSource on the next screen.

Hope this helps...

Re: Errors occured during extraction

Former Member — Mon, 20 Feb 2006 16:16:03 GMT

Hello,

I attempted to run RS_TRANSTRU_ACTIVATE_ALL in SE38. I ran it for -

Source System: BWD001

InfoSource: 80COPC_C09

Still no luck..

Any other ideas. I am starting to think this may be related to BW Support packs recently put in.

Thanks,

Nick

Re: Errors occured during extraction

Former Member — Mon, 20 Feb 2006 16:22:22 GMT

Hi Nick,

Rarely i use this program, only when i have several objects to activate.

In your case, i think the better way to do this is after replicating the datasources, go to the infosource with problems ( 0COPC_C09 ) and activate it manually.

Regards,

Tomas Prusaczyk

Re: Errors occured during extraction

Former Member — Mon, 20 Feb 2006 16:29:30 GMT

Sorry Nick,

I told you to activate manually the datasource 0COPC_C09 , but this is your infocube ...

If you are using the standard infosource, you have to activate the 0CO_PC_PCP_02, or your custom infosource.

Regards,

Tomas

Re: Errors occured during extraction

Former Member — Mon, 20 Feb 2006 16:37:09 GMT

Hello Tomas,

Thanks for the information. Yeah the 0COPC_C09 is my infocube. And I am able to load data to this infocube without any problems from 0CO_PC_PCP_02.

But the problem is when I am loading data from 0COPC_C09 to my ODS ZCOPC_05.

So I don't see how activating 0CO_PC_PCP_02 would help in this case.

Please correct me if I am wrong in my understanding. (and if I should still activate 0CO_PC_PCP_02, even though I can load data to 0COPC_C09)

Thanks,

Nick

Re: Errors occured during extraction

Former Member — Mon, 20 Feb 2006 16:53:54 GMT

Hum, ok Nick.

Di you try to run the RS_COMSTRU_ACTIVATE_ALL, for this infosource?

Regards,

Tomas

Re: Errors occured during extraction

Former Member — Mon, 20 Feb 2006 17:09:58 GMT

Hello Tomas,

I ran the RS_COMSTRU_ACTIVATE_ALL. I specified 80COPC_C09 as the infosource.

I got this message:

no inactive communication struture found

Message no. RSAR051

Thanks,

Nick

Re: Errors occured during extraction

Former Member — Tue, 28 Feb 2006 15:19:52 GMT

Hello Everyone,

The problem has been solved. Here was the solution:

The dataload is failing because the database TEMPDB does not have enough space available. Your TEMPDB is to small to handle the load from your cube. You are getting the following error, which can be seen in SM21 andST04:

[1101] Could not allocate new page for database 'TEMPDB'.

There are no more pages available in filegroup DEFAULT. Space can be created by dropping objects, adding additional files, or allowing file growth.

In other words, your database TEMPDB is full. You have to increase the free space within the database TEMPDB. Please increase the space with your DB administrators, and test the load again.

Once TEMPDB was adjusted and the system was rebooted the problem was solved.

Just wanted to share the resolution with future SDN'rs with the same problem.

Thanks,

Nick