I'm marking this a blocker even though it only should affect users who started out on Sakai 2.4 or earlier and have upgraded since then. We were looking at the database tables for GB_PERMISSION_T and FUNCTION_NAME was only varchar(5) because that's what the script (2.4-2.5) created it as and that was fine.
SAK-29812 it looks like a longer than 5 character value VIEW_COURSE_GRADE was added.
OOTB in MySQL FUNCTION_NAME is created as varchar (255) by hibernate and in Oracle it's VARCHAR2(255). Also USER_ID is also 255.
So for consistency these should both be increased to match the OOTB defaults and go in the 11.2 script.
ALTER TABLE GB_PERMISSION_T MODIFY FUNCTION_NAME VARCHAR(255);
ALTER TABLE GB_PERMISSION_T MODIFY USER_ID VARCHAR(255);
ALTER TABLE GB_PERMISSION_T MODIFY (FUNCTION_NAME VARCHAR2(255));
ALTER TABLE GB_PERMISSION_T MODIFY (USER_ID VARCHAR2(255));