there could be 1 things doing this

1. POBS tabes

2. Bad un-needed risk category types

to clean this mess up it is a 2 step process

step 1

clean the existing POBS tables from your existing database

I need to know if you ae using Microsoft sql or Oracel XE as your underlying database. One you tell me that I can provide the solution to clean your existing database.

step 2 

clean EVERY xer file prior to importing of un-necessary POBS tables and the bad Risk Types

here is the free utility to clean the xer files

http://scheduleanalyzer.com/PurgePOBS.exe

after you clean the xer file make sure to import the clean one. The utility will clena the xer file and create another xer with the word clean in the xer file name.

Joel that is software that he would have to pay for 

none of them do it just cleans Project Organizational Breakdown Structures that are not used on Primavera. As a matter of fact in the later releases of P6 they do not exist at all. 

no the POBS cleaner wii not delete anything. cleaning an xer file is only half of the solution. You need to clean your database of the POBS tables. Then prior to importing ANY xer files run them thru the cleaner. If using sql here are the instructions to clean you database. 

Go to Start

All Programs

Microsoft SQL Server 2005

SQL Server Management Express Studio

Server name: is name of computer

Authentication: SQL Server Authentication

Login: sa

Password: Prima123Vera

Click Connect

Click on Databases and expand it

Highlight pmdb$primavera

Up top select New Query

On the right hand side type delete pobs;

Then right click and select execute

Close SQL

Done

Prior to importing any XER file, always first open the XER file in NotePad and find the %T POBS records and remove that section from the file, save, then import the cleaned file.

Chris, Is POBS eraser a software?? can you please share the link.

We use PobsEraser - simple,  no admin restrictions. 

Reduces files quickly.  

Makes for a fast import.

Ian you need to clean the database and you need to clean ALL xer files prior to importing

Go to Start

All Programs

Microsoft SQL Server 2005

SQL Server Management Express Studio

Server name: is name of computer

Authentication: SQL Server Authentication

Login: sa

Password: Prima123Vera

Click Connect

Click on Databases and expand it

Highlight pmdb$primavera

Up top select New Query

On the right hand side type delete pobs;

Then right click and select execute

Close SQL

Done

now use any POBS cleaner to clean xe files prior to importing

Andrew has given you the solution for cleaning the POBS files after they have become xer files this is good for cleaning the files that you get from other users however this is only half of the solution your own database still has the POBS tables in there. So when YOU generate an xer file you will be giving someone an xer file with the POBS tables in it. You can clean the  xer file with the utility that Andrew has provided but then you can not use the function file send project.

So to solve the other half of the problem with the POBS tables is to clean the tables out from your database then remember to clean ALL xer files prior to importing them.

to clean the database  follow these instructions

http://pmsite.com/forums/viewthread/3322/

hey Mike

As per Oracle 

"Functions related to table POBS have not been implemented yet so the table has not been put to use. The table may be removed in a future release.

If there is data in this table, then it's probably present in the sample database and not inserted during operations performed in the application"

I see that you tried to install the sample projects. Did you try to install the sample projects in version 6.2 or 8.3 ?

If you imported a xer from someone that had a POBS in it then now you have it in your database.

So I have cleaned my database (this means NO POBS tables coming out of my system during an export of and xer file)

In order to prevent any POBs tables being imported INTO my database I always purge ALL xer files prior to importing them.This process eliminates all POBS tables in my database.

Eric if you want to prevent the tables from building up in the future I would suggest that you follow the above procedure. 

there are several POBS cleaners out there that will clean an xer file for you instead of doing it manually these are called purge programs 

Ron Winter has one

Emerald Associates has one 

and there is one included in the xertool kit program

to prevent this from happening again there is a two step process 

step 1

in order you YOUR system not to creaet POBS entries in xer files that you export you have to go into the microsoft slq database and run this script

delete from pobs; 

then right click and select execute

this will clean out an POBS tables that you currently have and will prevent any POBS tables being created when youexport and xer file

step 2 

always clean or purge ANY xer file before you import it into your database. This will prevent you from adding these tables back into your database.

here is what I have done to and it has reduced my database size by 50%

log into the sql database and run this script

delete from pobs; 

then right click and select execute

also before you import any xer files delete the POBS information as shown below I did this and a 7 meg file to to 1 meg

1. Open the XER in a text editor (example, notepad)
2. Find the line which reads:  %T POBS
3. Select the following lines within the XER until you reach the next %T:
   1. %T POBS
   2. %F (including all line content)
   3. %R (including all line content)
   4. Example:
      1. highlight this line --> %T POBS
      2. highlight this line --> %F pobs_id pobs_parent_id seq_num pobs_name pobs_descr pobs_manager
      3. highlight this line --> %R 100  0 POBS_Root Performing Organization_Root
   5. DO NOT HIGHLIGHT THIS LINE, ASSUMING THIS IS THE NEXT %T line listed in the XER file --> %T UDFTYPE
4. Delete all data highlighted from step 3.
   1. Note: The deleted data should only be the %T (table name line for POBS), %F (field names for POBS), %R (all POBS row data)
5. Save the XER file and close the text editor.

so you are deleting the info in the xer file from the %T POBS all the way to line right BEFORE the next %T

Import the updated XER file.

why not go into microsoft sql and shrik the file and the database

also a cleanup of the data base from time to time helps 

run these scripts

first run this one 

update statistics project with fullscan ,all

exec sp_updatestats 

and also this cleans up lost 

declare @ret integer, @msg varchar(255)