ORA-01653: unable to extend table DEV_MDS.MDS_ATTRIBUTES by 1024 in tablespace

Sometimes we get below error while deploying our bpel to server.
To solve this either contact your administrator requesting to extend the tablespace assigned to respective schema or if you have access of DB, perform below steps:

Problem:

ORA-01653: unable to extend table DEV_MDS.MDS_ATTRIBUTES by 1024 in tablespace DEV_MDS

How to fix:

C:\Users\admin>sqlplus sys/welcome1@XE as sysdba

SQL> alter tablespace DEV_MDS add datafile 'C:\ORACLEXE\ORADATA\XE\DEV_MDS2.DBF' size 1000M

Rotate log files

By default, when you start a WebLogic Server instance in development mode, the server automatically renames (rotates) its local server log file as SERVER_NAME.log00001, where SERVER_NAME is the name of the server. For the remainder of the server session, log messages accumulate in SERVER_NAME.log until the file grows to a size of 500 kilobytes.
Each time the server log file reaches this size, the server renames the log file using the syntax SERVER_NAME.lognnnnn, and creates a new SERVER_NAME.log to store new messages. By default, the rotated log files are numbered in order of creation using the syntax SERVER_NAME.lognnnnn, where SERVER_NAME is the name configured for the log file. You can configure a server instance to include a time and date stamp in the file name of rotated log files.
By default, when you start a server instance in production mode, the server rotates its local log file whenever the file grows to 5000 kilobytes in size. It does not rotate the local server log file when you start the server. For more information about changing the mode in which a server starts, see Change to production mode.
You can change these default settings for log file rotation. For example, you can change the file size at which the server rotates the log file or you can configure a server to rotate log files based on a time interval. You can also specify the maximum number of rotated files that can accumulate. After the number of log files reaches this number, subsequent file rotations overwrite the oldest log file.
Note: WebLogic Server sets a threshold size limit of 500 MB before it forces a hard rotation to prevent excessive log file growth.

call-template vs. apply-template

call-template:

<xsl:call-template name="somename"/>  is like calling a function in a traditional programming language.

we can define a function in XSLT like:
 
and then we can call this function using <xsl:call-template name="printname"/>,
 for ex.:

apply-templates: 

<xsl:apply-template> tag signals the XSLT processor to find the appropriate template to apply, based on the type and context of each selected node.
for example - below is our xml file:

and below is the xslt we are operating on above xml:


the output of this xslt will be:


or in html format: