Oracle BPM 11g MDS Error - Unable to Extend Table in Tablespace

Common error on BPM deployment and runtime is the engine cannot find a table or view and saying that it doesn't exist. Further investigation will result on the following error.

MDS-00001: exception in Metadata Services layer
MDS-00515: failure to save document /deployed-composites/default/ProjectName/businessCatalog/SchemaDataModule/XSD_NAME.xsd in the metadata repository 

 
ORA-01653: unable to extend table SCHEMANAME.TABLENAME by 1024 in tablespace TABLESPACENAME

This will mostly kill currently running application or fails a deployment.
Below is the solution that I take to solve the problem.

First, connect to your database as sysdba and execute this query.

select file_name,status from dba_data_files;

This query will return all the .dbf file location used by the system and its availability.
Find out the .dbf that produce the problem above. For my example, it will be soainfra table which file located on '/installPath/DEV1_soainfra.dbf'.

Take note on this location because we will use it for the next step.

Next step, execute this query and the location on highlighted 'part' based on the query above. Here's the example.

alter database datafile '/installPath/DEV1_soainfra.dbf' autoextend on maxsize unlimited;

That's it. We set the datafile to autoextend without maximum size so this problem will not reoccur. This should solve the problem on BPM application. Please note that due to the setting of unlimited autoextend, the server should have enough disk space to cater it.

Hope it helps. Cheers!

Solving Oracle BPM 11g Composite Error - Could not locate composite. Runtime Operation Error

When you've worked on many BPM composites, deploying and undeploying it over and over, someway, you could encounter this following error in the log.

<Mar 20, 2014 11:03:30 AM WIT> <Error> <oracle.soa.services.workflow.task> <BEA-000000> <<.> Could not locate composite.

Could not locate composite for workflow component default/PROJECTNAME!1.3.1*soa_1d2b1813-58f0-4264-8581-85013cd8eaba/CompositeName.

Ensure composite has been successfully deployed, and that the SOA server has completed loading composites.

ORABPEL-30084

Could not locate composite.

Could not locate composite for workflow component default/PROJECTNAME!1.3.1*soa_1d2b1813-58f0-4264-8581-85013cd8eaba/CompositeName.

Ensure composite has been successfully deployed, and that the SOA server has completed loading composites.

When you check on Enterprise Manager console (http://host:port/em), the composite is already undeployed but the workspace is still trying to find it, thus producing the following error possibilities in the BPM workspace (http://host:port/bpm/workspace):

"Runtime Operation Error"

"Could not perform the batch operation"

This thing can impact many things, starting from simple thing like user annoyance and also major thing like unaccessible Process Tracking and altering due to Runtime Operation Error.

Annoying as it is, but the solution is very simple.

Use your DB browser and access SOAINFRA schema. There, open WFTASKMETADATA table and delete any unused composite that prompt the error on the log.

Restart your MS, then try to access BPM workspace. The error will be no more.

Hope it helps!