Skip to Content
0
Former Member
Mar 24, 2008 at 09:08 PM

Cannot insert the value NULL into column 'SOURCE'

422 Views

System:

SAP BPC 5.1 SP1

Multi server - 1sql/1web

History:

We recently have been receiving several errors after we added an H3 to our Location (entity) dimension. The first issue we stumbled upon was the system was allowing users to send to parent members in the location dimension. This created several issues when we tried to optimize or process. Users were also getting the error, "Invalid use of Null;SaveMemberlistInfo" when sending data.

We usually schedule a dtsx package built w/SSIS to process all dimensions optimize overnight. When we ran into the above issues I cleared the data sent to the parent members and processed all dimensions thru Admin. This alleviated both previous problems but I ran into a new issue. When I tried to perform a full optimize, the log file grew to over 40GB, ran out of space and the process failed. We were able to run an incremental optimize with compress successfully. We were eventually able to run a full optimize by restricting the log file to 1GB. Also, during this series of steps we removed the H3 as we determined that may be the root cause.

I thought we were on the up and up until this weekend. Users again began to receive the “Invalid use of Null” error when sending data. I did a full process of all dimensions and once again it corrected the issue.

I am in the process of doing some testing in dev and when I run the SSIS package I receive an error, “Cannot insert the value NULL into column 'SOURCE'…” This is after it successfully rebuilds all of the dimensions. It occurs during the tasks that compress the Fac2, FactWB and Fact tables. More specifically, it occurs after all records have been combined in Fac2 and are being moved back to Fact.

My thoughts are that during these issues a null somehow found its way into one of the tables. ThatÂ’s the easy part. All tables are set up to not allow null values. I have also queried the Fact, Fac2 and FactWB tables for null values without success. Is there another table that could cause this? Is our DB corrupt?

Any thoughts/insight is greatly appreciated.

Thank you.

Edited by: Anton Chris on Mar 24, 2008 10:17 PM

Edited by: Anton Chris on Mar 24, 2008 10:20 PM