KB442346: Error “Failed to insert table DSSMDOBJLOCK” is found in DSSErrors log when triggering multiple subscriptions to user who doesn’t have Profile folder

SYMPTOM
Error “Failed to insert table DSSMDOBJLOCK” is found in DSSErrors log when triggering multiple subscriptions to a user who doesn’t have Profile folder.
Normally this error will be recorded when an object is locked by one operation and at the same time, another operation is trying to lock the same object also.
 
Here is a scenario where this error may be reproduced in Strategy:
1.Log in as Administrator and create a new user. Do not log in as this user to ensure there is no Profile folder created under this user account. Or manually remove the profile folders for this user from Developer.
2.Create two subscriptions which are set to this new user using a same schedule.
3.Trigger the schedule. Below error will be recorded in DSSErrors log:

2018-11-30 00:16:01.848-05:00 [HOST:ENV-118230WAIOU][SERVER:CastorServer][PID:4348][THR:3268][Database Classes][Error] Execute Query failed. 
Error type: Odbc error. Odbc operation attempted: SQLExecDirect. [23000:1: on SQLHANDLE] [Strategy][ODBC Oracle Wire Protocol driver][Oracle]ORA-00001: unique constraint (XILINOCA12.SYS_C002305191) violated
ORA-06512: at line 1 Connection String: DSN=XILINOCA12;UID=XILINOCA12;ENABLENCHARSUPPORT=1;ENABLEDESCRIBEPARAM=1;HOST=10.27.10.104;PORT=1521;SID=unicode;. SQL Statement: BEGIN INSERT INTO DSSMDOBJLOCK VALUES ('38A062302D4411D28E71006008960167', '9E2A92DB433EABE84AFC91BEF883E15B', 34, 0, 1, 7, TO_TIMESTAMP('2018-11-30 05:16:01.817','YYYY-MM-DD HH24:MI:SS.FF'), '16B8C8A0C509319025849029649B13E3', '00000000000000000000000002000000', 'ENV-118230WAIOU', 'Lock the profile folders because we''ll serialize profile creation.'); END;.
2018-11-30 00:35:43.383-05:00 [HOST:ENV-118230WAIOU][SERVER:CastorServer][PID:4348][THR:3268][MSql][Error] Error executing SQL: BEGIN INSERT INTO DSSMDOBJLOCK VALUES ('38A062302D4411D28E71006008960167', '9E2A92DB433EABE84AFC91BEF883E15B', 34, 0, 1, 7, TO_TIMESTAMP('2018-11-30 05:16:01.817','YYYY-MM-DD HH24:MI:SS.FF'), '16B8C8A0C509319025849029649B13E3', '00000000000000000000000002000000', 'ENV-118230WAIOU', 'Lock the profile folders because we''ll serialize profile creation.'); END;

CAUSE
This is a known behavior in Strategy with no harm.
When Intelligence Server executes a subscription, it will log in to the corresponding project as the subscription's recipient user. As the profile folder will be created at the 1st login of a new user or when the profile folders are deleted, Intelligence Server will attempt to create the profile folder for this user twice and almost simultaneously. 
Both will try to lock the object in metadata but only 1st request would succeed and the 2nd would fail, which leads to this error.
Actually, if the two subscriptions are not triggered at the same time, the 2nd request will find the profile folders already exist and it will not try to create it again. This error will not happen.
Also if this is not a newly created user who never logs in, the issue will not happen either.
Even when the issue happens, it has no impact to the whole functionality. It is just alert saying the 2nd request to create profile folder fails, which is expected behavior.
ACTION
Considering the nature of this corner issue, Strategy will not conduct any code change regarding this behavior.
The current logic could handle this scenario properly.
This error could be safely ignored if it is verified that the same situation as stated in this article happens.  
The Strategy Internal Reference Number for the issue discussed in this technical note is DE122034. KB442346