This was originally reported byu a user with a Moodle 3.1 server using Oracle as the database. They updated BigBluebuttonBN from 2.2.2 to 2.2.6.

The issue is that Oracle is more strict when dealing with non-null fileds. The plugin has defined meetingid as non-null, but is creating the instance with meetingid empty. Once the instance is created, the id assigned is used for filling up the missing field.

The database schema should be updated to allow null, BUT, it may be better to go with a workaround and no to add this database change for the release, unless another change to the database is required.

Workaround:

Just add before inserting the instance

$meetingid = 0;